Patent Grant
10365819
This relates generally to electronic devices with touch-sensitive surfaces, including but not limited to electronic devices with touch-sensitive surfaces that are used to navigate and annotate an electronic document.
The use of touch-sensitive surfaces as input devices for computers and other electronic computing devices has increased significantly in recent years. Exemplary touch-sensitive surfaces include touch pads and touch screen displays. Such surfaces are widely used to manipulate user interface objects on a display.
Exemplary manipulations include navigating through, and annotating an electronic document, such as an electronic book, newspaper, or magazine. A user may need to perform such manipulations in an electronic book or document reader application or in a digital publication application, for example.
But existing methods for navigating and annotating are cumbersome and inefficient. In addition, existing methods take longer than necessary, thereby wasting energy. This latter consideration is particularly important in battery-operated devices.
Accordingly, there is a need for electronic devices with faster, more efficient methods and interfaces for navigating and annotating an electronic document. Such methods and interfaces may complement or replace conventional methods for navigating and annotating an electronic document. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated devices, such methods and interfaces conserve power and increase the time between battery charges.
The above deficiencies and other problems associated with user interfaces for electronic devices with touch-sensitive surfaces are reduced or eliminated by the disclosed devices. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a notebook computer, tablet computer, or handheld device). In some embodiments, the device has a touchpad. In some embodiments, the device has a touch-sensitive display (also known as a “touch screen” or “touch screen display”). In some embodiments, the device has a graphical user interface (GUI), one or more processors, memory and one or more modules, programs or sets of instructions stored in the memory for performing multiple functions. In some embodiments, the user interacts with the GUI primarily through finger contacts and gestures on the touch-sensitive surface. In some embodiments, the functions may include image editing, drawing, presenting, word processing, website creating, disk authoring, spreadsheet making, game playing, telephoning, video conferencing, e-mailing, instant messaging, workout support, digital photographing, digital videoing, web browsing, digital music playing, and/or digital video playing. Executable instructions for performing these functions may be included in a non-transitory computer readable storage medium or other computer program product configured for execution by one or more processors.
In accordance with some embodiments, a method is performed at an electronic device with a display and a touch-sensitive surface. The device is configured to operate in a first operational mode at some times and in a second operational mode distinct from the first operational mode at other times. The method includes detecting a first gesture on the touch-sensitive surface having a first gesture type, and in response to detecting the first gesture: in accordance with a determination that the device is in the first operational mode, performing an operation having a first operation type, and in accordance with a determination that the device is in the second operational mode, performing an operation having a second operation type distinct from the first operation type. The method also includes detecting a second gesture on the touch-sensitive surface having a second gesture type distinct from the first gesture type, and in response to detecting the second gesture: in accordance with a determination that the device is in the first operational mode, performing an operation having the second operation type, and in accordance with a determination that the device is in the second operational mode, performing an operation having the first operation type.
In accordance with some embodiments, an electronic device includes a display, a touch-sensitive surface, one or more processors, memory, and one or more programs. The device is configured to operate in a first operational mode at some times and in a second operational mode distinct from the first operational mode at other times. The one or more programs are stored in the memory and configured to be executed by the one or more processors and the one or more programs include instructions for performing the operations of the method described above. In accordance with some embodiments, a graphical user interface on an electronic device with a display, a touch-sensitive surface, a memory, and one or more processors to execute one or more programs stored in the memory includes one or more of the elements displayed in the method described above, which are updated in response to inputs, as described in the method above. In accordance with some embodiments, a non-transitory computer readable storage medium has stored therein instructions which when executed by an electronic device with a display and a touch-sensitive surface cause the device to perform the operations of the method described above. In accordance with some embodiments, an electronic device includes: a display; a touch-sensitive surface; and means for performing the operations of the method described above. In accordance with some embodiments, an information processing apparatus, for use in an electronic device with a display and a touch-sensitive surface, includes means for performing the operations of the method described above.
In accordance with some embodiments, a method is performed at an electronic device with a touch-sensitive display and a touch-sensitive surface that is distinct from the touch-sensitive display. The method includes detecting a predefined gesture, and in response to detecting the predefined gesture, displaying a character input user interface on the display. In accordance with detection of the predefined gesture on the touch-sensitive surface, the character input user interface includes a split keyboard. In accordance with detection of the predefined gesture on the touch-sensitive display, the character input user interface includes an unsplit keyboard.
In accordance with some embodiments, an electronic device includes a touch-sensitive display, a touch-sensitive surface distinct from the touch-sensitive display, one or more processors, memory, and one or more programs; the one or more programs are stored in the memory and configured to be executed by the one or more processors and the one or more programs include instructions for performing the operations of the method described above. In accordance with some embodiments, a graphical user interface on an electronic device with a touch-sensitive display, a touch-sensitive surface distinct from the touch-sensitive display, a memory, and one or more processors to execute one or more programs stored in the memory includes one or more of the elements displayed in the method described above, which are updated in response to inputs, as described in any of the methods above. In accordance with some embodiments, a computer readable storage medium has stored therein instructions which when executed by an electronic device with a touch-sensitive display and a touch-sensitive surface distinct from the touch-sensitive display, cause the device to perform the operations of the method described above. In accordance with some embodiments, an electronic device includes: a touch-sensitive display, and a touch-sensitive surface distinct from the touch-sensitive display, and means for performing the operations of the method described above. In accordance with some embodiments, an information processing apparatus, for use in an electronic device with a touch-sensitive display and a touch-sensitive surface distinct from the touch-sensitive display, includes means for performing the operations of the method described above.
In accordance with some embodiments, a method is performed at an electronic device with a display and a touch-sensitive surface. The method includes displaying a document having a user-specified highlighted area that includes highlighting of a first type, detecting a contact at an initial contact location on the touch-sensitive surface that corresponds to an initial location on the display, detecting movement of the contact on the touch-sensitive surface, and, in response to detecting the movement of the contact on the touch-sensitive surface, in accordance with a determination that the initial location on the display is within the highlighted area, adding highlighting of a second type distinct from the first type to at least a portion of the highlighted area.
In accordance with some embodiments, an electronic device includes a display, a touch-sensitive surface, one or more processors, memory, and one or more programs; the one or more programs are stored in the memory and configured to be executed by the one or more processors and the one or more programs include instructions for performing the operations of any of the methods described above. In accordance with some embodiments, a graphical user interface on an electronic device with a display, a touch-sensitive surface, a memory, and one or more processors to execute one or more programs stored in the memory includes one or more of the elements displayed in any of the methods described above, which are updated in response to inputs, as described in any of the methods above. In accordance with some embodiments, a computer readable storage medium has stored therein instructions which when executed by an electronic device with a display and a touch-sensitive surface, cause the device to perform the operations of any of the methods described above. In accordance with some embodiments, an electronic device includes: a display; a touch-sensitive surface; means for performing the operations of any of the methods described above. In accordance with some embodiments, an information processing apparatus, for use in an electronic device with a display and a touch-sensitive surface, includes means for performing the operations of any of the methods described above.
In accordance with some embodiments, an electronic device, configured to operate in a first operational mode at some times and in a second operational mode distinct from the first operational mode at other times, includes a display unit; a touch-sensitive surface unit configured to receive user gestures; and a processing unit coupled to the display unit and the touch-sensitive surface unit. The processing unit is configured to detect a first gesture on the touch-sensitive surface unit having a first gesture type, and in response to detecting the first gesture: in accordance with a determination that the electronic device is in the first operational mode, perform an operation having a first operation type; and in accordance with a determination that the electronic device is in the second operational mode, perform an operation having a second operation type distinct from the first operation type. The processing unit is also configured to detect a second gesture on the touch-sensitive surface unit having a second gesture type distinct from the first gesture type; and in response to detecting the second gesture: in accordance with a determination that the electronic device is in the first operational mode, perform an operation having the second operation type; and in accordance with a determination that the electronic device is in the second operational mode, perform an operation having the first operation type.
In accordance with some embodiments, an electronic device includes a touch-sensitive display unit configured to receive user gestures; a touch-sensitive surface unit, distinct from the touch-sensitive display unit, configured to receive user gestures; and a processing unit coupled to the touch-sensitive display unit and the touch-sensitive surface unit. The processing unit is configured to detect a predefined gesture, and in response to detecting the predefined gesture, enable display of a character input user interface on the touch-sensitive display unit. In accordance with detection of the predefined gesture on the touch-sensitive surface unit, the character input user interface includes a split keyboard. In accordance with detection of the predefined gesture on the touch-sensitive display unit, the character input user interface includes an unsplit keyboard.
In accordance with some embodiments, an electronic device includes a display unit configured to display a document having a user-specified highlighted area that includes highlighting of a first type; a touch-sensitive surface unit configured to receive user gestures; and a processing unit coupled to the display unit and the touch-sensitive surface unit. The processing unit is configured to detect a contact at an initial contact location on the touch-sensitive surface unit that corresponds to an initial location on the display unit, detect movement of the contact on the touch-sensitive surface unit, and, in response to detecting the movement of the contact on the touch-sensitive surface unit, in accordance with a determination that the initial location on the display unit is within the highlighted area, add highlighting of a second type distinct from the first type to at least a portion of the highlighted area.
Thus, electronic devices with displays and touch-sensitive surfaces are provided with faster, more efficient methods and interfaces for navigating and annotating an electronic document, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace conventional methods for navigating and annotating an electronic document.
For a better understanding of the aforementioned embodiments of the invention as well as additional embodiments thereof, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
Described below are devices and methods that enable a user to manipulate electronic documents, including navigating and annotating the electronic document and accessing character input interfaces.
In one method, a first gesture activates a first operation (e.g., a navigation operation such as turning a page in the electronic document) when the device is operating in a first mode (e.g., a navigation mode). The same first gesture activates a second operation (e.g., an annotation operation such as highlighting a portion of the page) when the device is operating in a second mode (e.g., an annotation mode). Conversely, a second gesture activates the first operation (e.g., the navigation operation) when the device is operating in the second mode (e.g., the annotation mode). The same second gesture activates the second operation (e.g., the annotation operation) when the device is operating in the first mode (e.g., the navigation mode). The first gesture is typically a simpler gesture than the second gesture. For example, the first gesture is a drag gesture and the second gesture is a tap and drag gesture. Thus, for example, simpler gestures are used to perform navigation operations when the device is in a navigation mode and the same simpler gestures are used to perform annotation operations when the device in an annotation mode. Yet annotation operations may still be performed when in the navigation mode (without switching to the annotation mode) by using the more complex gestures. Similarly, navigation operations may still be performed when in the annotation mode (without switching to the navigation mode) by using the same more complex gestures.
In another method, the device displays an unsplit or split keyboard depending on where a gesture to activate display of the keyboard is detected. The unsplit keyboard is displayed if the gesture is detected on the device's touch-sensitive display. The split keyboard is displayed if the gesture is detected on a touch-sensitive surface distinct from the touch-sensitive display (e.g., a touch-sensitive surface on the backside of the device). By displaying an unsplit or split keyboard depending on which touch-sensitive surface the gesture is performed on, the device displays a keyboard best suited to how the device is supported at that moment. When the gesture is performed on the touch sensitive display, the device is likely resting on a surface and thus suited for ten-finger typing with an unsplit keyboard. When the gesture is performed on the backside of the device, the device is likely being held by the user with the user's non-thumb fingers and thus suited for two-thumb typing using a split keyboard.
In another method, the device enables a user to easily and efficiently add a second type of highlighting to text already highlighted with a first type of highlighting. When text is displayed with one type of highlighting, in response to a gesture detected within the highlighted area, the device adds highlighting of a second type to the text along the path of the gesture. The second level of highlighting allows the user to add additional emphasis to parts of already-highlighted text.
Below,
Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be apparent to one of ordinary skill in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.
It will also be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first contact could be termed a second contact, and, similarly, a second contact could be termed a first contact, without departing from the scope of the present invention. The first contact and the second contact are both contacts, but they are not the same contact.
The terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the description of the invention and the appended claims, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
As used herein, the term “if” may be construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” may be construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touch pads), may also be used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touch pad).
In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device may include one or more other physical user-interface devices, such as a physical keyboard, a mouse and/or a joystick.
The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
The various applications that may be executed on the device may use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device may be adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device may support the variety of applications with user interfaces that are intuitive and transparent to the user.
Attention is now directed toward embodiments of portable devices with touch-sensitive displays.
It should be appreciated that device 100 is only one example of a portable multifunction device, and that device 100 may have more or fewer components than shown, may combine two or more components, or may have a different configuration or arrangement of the components. The various components shown in
Memory 102 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory 102 by other components of device 100, such as CPU 120 and the peripherals interface 118, may be controlled by memory controller 122.
Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data.
In some embodiments, peripherals interface 118, CPU 120, and memory controller 122 may be implemented on a single chip, such as chip 104. In some other embodiments, they may be implemented on separate chips.
RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 may include well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 may communicate with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The wireless communication may use any of a plurality of communications standards, protocols and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data may be retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212,
I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals interface 118. I/O subsystem 106 may include display controller 156 and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input or control devices 116. The other input control devices 116 may include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 may be coupled to any (or none) of the following: a keyboard, infrared port, USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208,
Touch-sensitive display 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch screen 112. Touch screen 112 displays visual output to the user. The visual output may include graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output may correspond to user-interface objects.
Touch screen 112 has a touch-sensitive surface, sensor or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 and converts the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages or images) that are displayed on touch screen 112. In an exemplary embodiment, a point of contact between touch screen 112 and the user corresponds to a finger of the user.
Touch screen 112 may use LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies may be used in other embodiments. Touch screen 112 and display controller 156 may detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, Calif.
Touch screen 112 may have a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user may make contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
In some embodiments, in addition to the touch screen, device 100 may include a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad may be a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.
Device 100 also includes power system 162 for powering the various components. Power system 162 may include a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
Device 100 may also include one or more optical sensors 164.
Device 100 may also include one or more proximity sensors 166.
Device 100 may also include one or more accelerometers 168.
In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments memory 102 stores device/global internal state 157, as shown in
Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with the 30-pin connector used on iPod (trademark of Apple Inc.) devices.
Contact/motion module 130 may detect contact with touch screen 112 (in conjunction with display controller 156) and other touch sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, may include determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations may be applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.
Contact/motion module 130 may detect a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns. Thus, a gesture may be detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (lift off) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (lift off) event.
Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the intensity of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including without limitation text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations and the like.
In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic may be assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.
Text input module 134, which may be a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).
GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing, to camera 143 as picture/video metadata, and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
Applications 136 may include the following modules (or sets of instructions), or a subset or superset thereof:
Examples of other applications 136 that may be stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, contacts module 137 may be used to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference 139, e-mail 140, or IM 141; and so forth.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, telephone module 138 may be used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in address book 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation and disconnect or hang up when the conversation is completed. As noted above, the wireless communication may use any of a plurality of communications standards, protocols and technologies.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, videoconferencing module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages and to view received instant messages. In some embodiments, transmitted and/or received instant messages may include graphics, photos, audio files, video files and/or other attachments as are supported in a MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, books module 142 includes executable instructions to display, annotate, and share an electronic book (e.g., a text book), magazine, newspaper or other digital publication between a user and one or more other participants in accordance with user instructions.
In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.
In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.
In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.
In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to do lists, etc.) in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that may be downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 may be used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).
In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.
In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present or otherwise play back videos (e.g., on touch screen 112 or on an external, connected display via external port 124). In some embodiments, device 100 may include the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to do lists, and the like in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 may be used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions; data on stores and other points of interest at or near a particular location; and other location-based data) in accordance with user instructions.
In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video.
Each of the above identified modules and applications correspond to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various embodiments. In some embodiments, memory 102 may store a subset of the modules and data structures identified above. Furthermore, memory 102 may store additional modules and data structures not described above.
In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 may be reduced.
The predefined set of functions that may be performed exclusively through a touch screen and/or a touchpad include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that may be displayed on device 100. In such embodiments, the touchpad may be referred to as a “menu button.” In some other embodiments, the menu button may be a physical push button or other physical input control device instead of a touchpad.
Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch sensitive display 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.
In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.
Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.
In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripheral interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).
In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.
Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views, when touch sensitive display 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.
Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected may correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected may be called the hit view, and the set of events that are recognized as proper inputs may be determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (i.e., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.
Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.
Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver module 182.
In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 may utilize or call data updater 176, object updater 177 or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 includes one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.
A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170, and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which may include sub-event delivery instructions).
Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch the event information may also include speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.
Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event 187 include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first lift-off (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second lift-off (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display 112, and lift-off of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.
In some embodiments, event definition 187 includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.
In some embodiments, the definition for a respective event 187 also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.
When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.
In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers may interact with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.
In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.
In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.
In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module 145. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 176 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.
In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input-devices, not all of which are initiated on touch screens, e.g., coordinating mouse movement and mouse button presses with or without single or multiple keyboard presses or holds, user movements taps, drags, scrolls, etc., on touch-pads, pen stylus inputs, movement of the device, oral instructions, detected eye movements, biometric inputs, and/or any combination thereof, which may be utilized as inputs corresponding to sub-events which define an event to be recognized.
Device 100 may also include one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 may be used to navigate to any application 136 in a set of applications that may be executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.
In one embodiment, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, Subscriber Identity Module (SIM) card slot 210, head set jack 212, and docking/charging external port 124. Push button 206 may be used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also may accept verbal input for activation or deactivation of some functions through microphone 113.
Each of the above identified elements in
Attention is now directed towards embodiments of user interfaces (“UI”) that may be implemented on portable multifunction device 100.
Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that may be implemented on an electronic device with a display and a touch-sensitive surface, such as device 300 or portable multifunction device 100.
In some embodiments, electronic document 501 is displayed on display 112 in one of two modes—a navigation mode or an annotation mode. When electronic document 501 is displayed in navigation mode, the focus is on efficient navigation (e.g., navigating between pages and between chapters, scrolling, etc.); simple gestures are directed to navigation operations, and more complex gestures (e.g., composite gestures with multiple components, such as a tap plus a swipe) are directed to other operations or features (e.g., annotation). When electronic document 501 is displayed in annotation mode, the focus is on efficient annotation (e.g., commenting, highlighting, bookmarking, etc.); simple gestures are directed to annotation operations, and more complex gestures are directed to other operations or features (e.g., navigation). In
Gesture 506 by a user is detected on touch-sensitive display 112. Gesture 506 includes movement in direction 507. In some embodiments, gesture 506 is a swipe or drag gesture.
In
Gesture 518 by the user is detected on touch-sensitive display 112 over text portion 508-2. Gesture 518 includes movement in direction 520. Gesture 518 is the same type of gesture as gesture 506 (
In
In some embodiments, when displaying electronic document 501, device 100 toggles between navigation mode and annotation mode in response to the detection of a predefined gesture (e.g., gestures 526 and/or 528 or some other predefined gesture).
Gestures 526 and/or 528 by the user are detected on touch-sensitive display 112. In some embodiments, both gestures 526 and 528 are drumming gestures, each using a respective hand (e.g., gesture 526 is performed using the left hand and gesture 528 the right hand). For example, gesture 526 includes finger contacts 526-A thru 526-D detected in sequence, and gesture 528 includes finger digit contacts 528-A thru 528-D detected in sequence. In gesture 526, contact 526-A (corresponding to the left pinky) is detected first, then contact 526-B (corresponding to the left ring finger), then contact 526-C (corresponding to the left middle finger), and then contact 526-D (corresponding to the left index finger). The sequence of detected contacts is analogous for gesture 528 using the right hand. In some embodiments, gesture 526 and/or 528 correspond to a predefined gesture for toggling between annotation mode and navigation mode, as described above; depending on the embodiment, the predefined gesture includes a drumming gesture using one hand (as in either gesture 526 or 528) or both hands (as in both gesture 526 and 528 detected simultaneously or within a predefined time period of each other (e.g., less than 0.5 second apart).
In response to detection of gesture 526 and/or 528, device 100 switches to navigation mode, as shown in
While electronic document 501 is displayed in navigation mode, as shown in
Gestures 530 and/or 532 by the user are detected on touch-sensitive display 112. In some embodiments, gestures 530 and 532 are drumming gestures. Gestures 530 and 532 are analogous to gestures 526 and 528, respectively, and thus further details are omitted here.
In response to detection of gestures 530 and/or 532 (depending on the embodiment, one or both hands performing the drumming gesture is needed), soft keyboard 534 is displayed on display 112, as shown in
In some embodiments, the touch-sensitive surface distinct from touch-sensitive display 112 is on the side of the device opposite of touch-sensitive display 112 (e.g., touch-sensitive display 112 is on the front side and the distinct touch-sensitive surface is on the back side). Examples of touch-sensitive surfaces distinct from the touch-sensitive display are disclosed in U.S. patent application Ser. No. 12/849,769, titled “Device, Method, and Graphical User Interface with Enhanced Touch Targeting,” filed Aug. 3, 2010, which is incorporated by reference herein in its entirety.
Gestures 538 and 540 are detected on the touch-sensitive surface on the back side of device 100. In some embodiments, gestures 538 and 540 are each drumming gestures. For example, gesture 538 includes finger contacts 538-A thru 538-D detected in sequence, and gesture 540 includes finger digit contacts 540-A thru 540-D detected in sequence. In gesture 538, contact 538-A (corresponding to the left pinky) is detected first, then contact 538-B (corresponding to the left ring finger), then contact 538-C (corresponding to the left middle finger), and then contact 538-D (corresponding to the left index finger). The sequence of detected contacts is analogous for gesture 540 using the right hand.
In response to detection of gestures 538 and/or 540 (depending on the embodiment, one or both hands performing the drumming gesture is needed), integrated input area 541 with split soft keyboard 542 is displayed on display 112, as shown in
Gesture 548 by the user, over text segment 546, is detected on touch-sensitive display 112. Text segment 546 is within the portion of body text 543 that is highlighted by highlighting 544. Gesture 548 includes movement in direction 550 and is initiated at a location on display 112 corresponding to a location within highlighting 544. In some embodiments, gesture 548 is a swipe gesture.
In
In
In
As described below, the method 600 provides an intuitive way to navigate and annotate an electronic document. The method simplifies the procedure for navigation when a navigation-focused mode is active, yet still enables annotation in the navigation-focused mode. Conversely, the method simplifies the procedure for annotation when an annotation-focused mode is active, yet still enables navigation in the annotation-focused mode. For battery-operated electronic devices, enabling a user to navigate and annotate an electronic document faster and more efficiently conserves power and increases the time between battery charges.
The method 600 is performed at an electronic device having a display and a touch-sensitive surface, where the device is configured to operate in a first operational mode at some times and in a second operational mode distinct from the first operational mode at other times (602). In other words, during a first time period the device operates in the first operational mode, and during a second time period the device operates in the second operational mode, and the first time period does not overlap with the second time period (e.g., the device switches from a navigation mode to an annotation mode in response to user input). For example, device 100 (
In some embodiments, the first operational mode is a navigation-preferred mode; and the second operational mode is an annotation-preferred mode (604). For example, as described above with reference to
In some embodiments, while the device is in a navigation-preferred mode, a plurality of simple gestures are associated with corresponding basic navigation operations, and a plurality of composite gestures are associated with corresponding basic annotation operations, where a composite gesture has multiple components including a single continuous contact on the touch-sensitive surface and at least one other component (606). In other words, in navigation-preferred mode, navigation is preferred and can thus be performed using simple gestures, but annotation is possible using more complex gestures. In some embodiments, a simple gesture consists of a single continuous contact on the touch-sensitive surface, such as a drag or swipe gesture. In some embodiments, a composite gesture includes a simple gesture and one or more additional gesture components (e.g., taps, swipes, additional contacts, etc.).
In some embodiments, while the device is in an annotation-preferred mode, a plurality of simple gestures are associated with corresponding basic annotation operations; and a plurality of composite gestures are associated with corresponding basic navigation operations, where a composite gesture has multiple components including a single continuous contact on the touch-sensitive surface and at least one other component (608). In other words, in annotation-preferred mode, annotation is preferred and can thus be performed using simple gestures, but navigation is possible using more complex gestures. In some embodiments, a simple gesture consists of a single continuous contact on the touch-sensitive surface, such as a drag or swipe gesture. In some embodiments, a composite gesture includes a simple gesture and one or more additional gesture components (e.g., taps, swipes, additional contacts, etc.).
For example, as described above with reference to
The device detects a first gesture on the touch-sensitive surface having a first gesture type (e.g., a swipe gesture) (610). For example, in
In response to detecting the first gesture (612), in accordance with a determination that the device is in the first operational mode, the device performs an operation having a first operation type (e.g., navigate) (614); and in accordance with a determination that the device is in the second operational mode, the device performs an operation having a second operation type distinct from the first operation type (e.g., highlight) (616). For example, in
In some embodiments, the operation performed at the device in response to detecting the first gesture is determined based at least in part on a location and/or direction of the first gesture on the touch-sensitive surface (618). For example, if the operation performed at the device in response to detecting the first gesture is a highlighting operation, the highlighted portion of the document is a portion of the document proximate to a location on the display that corresponds to a location of the first gesture on the touch-sensitive surface. In contrast, if the operation performed at the device in response to detecting the first gesture is a navigation operation, the document advances to another portion in accordance with the direction of the first gesture (e.g., a swipe to the right may navigate to a previous page of the document while a swipe to the left navigates to a next page of the document). For example, in
The device detects a second gesture on the touch-sensitive surface having a second gesture type (e.g., a tap and swipe gesture) distinct from the first gesture type (620). For example, in
In response to detecting the second gesture (622), in accordance with a determination that the device is in the first operational mode, the device performs an operation having the second operation type (e.g., highlight) (624), and in accordance with a determination that the device is in the second operational mode, the device performs an operation having the first operation type (e.g., navigate) (626). For example, in
In some embodiments, the operation performed at the device in response to detecting the second gesture is determined based at least in part on a location and/or direction of the second gesture on the touch-sensitive surface (628). For example, if the operation performed at the device in response to detecting the second gesture is a highlighting operation, the highlighted portion of the document is a portion of the document proximate to a location on the display that corresponds to a location of the second gesture on the touch-sensitive surface. In contrast, if the operation performed at the device in response to detecting the second gesture is a navigation operation, the document advances to another portion in accordance with the direction of the second gesture (e.g., a swipe to the right may navigate to a previous page of the document while a swipe to the left navigates to a next page of the document). For example, in
In some embodiments, the display is displaying an electronic document (e.g., a webpage, word processing document, spreadsheet, desktop publishing document, slideshow document, drawing document, book, etc.), the first operation type is a navigation operation (e.g., advancing through pages of a document and/or scrolling through a document in one or two dimensions), and the second operation type is an annotation operation (e.g., highlighting text in the document or adding a note or other annotation to a portion of the document) (630). For example, in
In some embodiments, the first gesture type is simpler to perform than the second gesture type (632). In some embodiments, the second gesture includes all of the components of the first gesture and additional components that occur prior to or after the components of the first gesture type. For example, gesture 506 may be a swipe gesture, and gesture 510 may be a tap gesture 510-1 plus a swipe gesture 510-2.
In some embodiments, the first gesture type is a swipe gesture and the second gesture type is a tap and swipe gesture (634). For example, gesture 506 may be a swipe gesture, and gesture 510 may be a tap and swipe gesture (tap gesture 510-1 plus swipe gesture 510-2). In some embodiments, the first gesture type is a tap and swipe gesture and the second gesture type is a double tap and swipe gesture (not shown).
In some embodiments, the first gesture type is single contact gesture and the second gesture type is a multi contact gesture. (e.g., the first gesture type is a single contact swipe, and the second gesture type is a single contact swipe while simultaneously detecting an additional “chording” contact) (636). For example, the first gesture type may be a swipe gesture, and the second gesture type may be a swipe gesture plus a simultaneous, distinct finger contact (e.g., using another finger digit on the hand not performing the swipe gesture) on the touch-sensitive surface. As an example, gesture 510 (
In some embodiments, the device switches from the first operational mode to the second operational mode in response to detecting a predefined gesture (638). In some embodiments, the predefined gesture is a sequential multi-contact gesture (e.g., a “finger drumming gesture”), as described in greater detail below. In some embodiments, when the device detects the same predefined gesture while the device is already in the second operational mode, the device switches or toggles from the second operational mode to the first operational mode.
In some embodiments, the device switches from the first operational mode to the second operational mode in response to detecting a finger drumming gesture on the touch-sensitive surface (e.g., a sequential multi-contact gesture that is consistent with a person drumming their non-thumb fingers on the touch-sensitive surface) (640). For example, device 100, while displaying electronic document 501, may switch from annotation mode to navigation mode, and vice versa, in response to drumming gesture(s) 526 and/or 528 (depending on the embodiment, the predefined gesture is a drumming gesture using one hand or a gesture with both hands drumming substantially simultaneously). Gesture 526 includes contacts 526-A thru 526-D detected in sequence. Gesture 528 includes contacts 528-A thru 526-D detected in sequence.
In some embodiments, the finger drumming gesture is a two-handed finger drumming gesture (642). For example, the predefined finger drumming gesture may be gestures 526 (left hand) and 528 (right hand) performed substantially simultaneously (e.g., within 0.5 seconds of each other).
In some embodiments, the device includes a touch-sensitive surface that is distinct from the display and the touch sensitive surface is positioned on a side of the device (e.g., the back) that does not include the display (644). For example, as described above with reference to
In some embodiments, the device displays a graphical user interface element in response to switching from the first operational mode to the second operational mode (646). In some embodiments, the graphical user interface element is a keyboard, a game controller, etc. For example, when device 100 switches from navigation mode to annotation mode, annotation toolbar 516 may be displayed.
In some embodiments, a method for navigating and annotating an electronic document is performed at an electronic device having a display and a touch-sensitive surface. The method includes, while the device is in a first operational mode (e.g., navigation mode): detecting a first gesture on the touch-sensitive surface having a first gesture type (e.g., tap and swipe), and in response to detecting the first gesture, performing a first operation having a first operation type (e.g., navigate); and detecting a second gesture on the touch-sensitive surface having a second gesture type (e.g., double tap and swipe) that is distinct from the first gesture type, and in response to detecting the second gesture, performing a second operation having a second operation type (e.g., highlight) that is distinct from the first operation type. The method also includes, while the device is in a second operational mode; detecting a third gesture on the touch-sensitive surface having the first gesture type (e.g., tap and swipe), and in response to detecting the third gesture, performing a third operation having the second operation type (e.g., highlight); and detecting the fourth gesture on the touch-sensitive surface having the second gesture type (e.g., double tap and swipe), and in response to detecting the fourth gesture, performing a fourth operation having the first operation type (e.g., navigate).
For example, in
As described below, the method 700 provides an intuitive way to display a split keyboard or an unsplit keyboard. The method displays a keyboard best suited to the user's likely hand position, thereby creating a more efficient text entry experience. For battery-operated electronic devices, enabling a user to display the proper keyboard faster and more efficiently conserves power and increases the time between battery charges.
The method is performed at an electronic device having a touch-sensitive display and a touch-sensitive surface that is distinct from the touch-sensitive display (702). In some embodiments, the touch-sensitive display is located on a first side (e.g., the front side of a tablet computer or the top inner side of clamshell/notebook computer) of the device and the touch-sensitive surface is located on a second side (e.g., the back side of a tablet computer or the bottom inner side of a clamshell/notebook computer) of the device that is distinct from the first side (704). For example, device 100 as illustrated in
The device detects a predefined gesture (706). In some embodiments, the predefined gesture is a finger drumming gesture (e.g., a sequential multi-contact gesture that is consistent with a person drumming their fingers on the touch-sensitive surface) (708). For example, in
In response to detecting the predefined gesture, the device displays a character input user interface on the display (710). The character input user interface includes a soft keyboard which is split or unsplit, depending on where the predefined gesture is detected.
In accordance with detection of the predefined gesture on the touch-sensitive surface, the character input user interface includes a split keyboard (e.g., as part of an integrated input area) (712). In some embodiments, a split keyboard includes a right side having a first plurality of character keys and a left side having a second plurality of character keys. In some embodiments, the first plurality includes one or more character keys that are not included in the second plurality. In some embodiments, the second plurality includes one or more character keys that are not included in the first plurality. In some embodiments, the first plurality is distinct from the second plurality. For example, in response to detection of gestures 538/540 and a determination that gestures 538/540 are detected on the distinct touch-sensitive surface, integrated input area 541 with split soft keyboard 542 is displayed on display 112.
In accordance with detection of the predefined gesture on the touch-sensitive display, the character input user interface includes an unsplit keyboard. (e.g., a single, unitary or merged keyboard that includes character keys from the left and right sides of the split keyboard) (714). For example, in response to detection of gestures 530/532 and a determination that gestures 530/532 are detected on touch-sensitive display 112, unsplit soft keyboard 534 is displayed on display 112.
By displaying a split or unsplit keyboard depending on which touch-sensitive surface the gesture is performed, the device displays a keyboard best suited to how the user is holding the device at that moment (with the gesture on the display corresponding to the device placed on a surface, and thus suited for touch typing with the unsplit keyboard; and the gesture on the touch-sensitive surface corresponding to the user holding the device with one or both hands, and thus suited for two-thumb typing with a split keyboard.
As described below, the method 800 provides an intuitive way to add a second type of highlighting to part of an area that is already highlighted. The method reduces the cognitive burden on a user when adding a second type of highlighting, as the complexity of the procedure to add the second type of highlighting is reduced. For battery-operated electronic devices, enabling a user to annotate an electronic document faster and more efficiently conserves power and increases the time between battery charges.
The device displays a document having a user-specified highlighted area that includes highlighting of a first type (802). For example, in
The device detects a contact at an initial contact location on the touch-sensitive surface that corresponds to an initial location on the display (804). For example, in
The device detects movement of the contact on the touch-sensitive surface (806). For example, gesture 548 (
In response to detecting the movement of the contact on the touch-sensitive surface, in accordance with a determination that the initial location on the display is within the highlighted area, the device adds highlighting of a second type distinct from the first type to at least a portion of the highlighted area (e.g., in accordance with the movement of the contact) (808). For example, in response to detection of gesture 548 over text portion 546, text portion 546 is underlined with underlining 552, as illustrated in
In some embodiments, the highlighting of the second type is coextensive with at least a portion of the highlighting of the first type (810). For example, if a particular paragraph of text is already highlighted with yellow highlighting (e.g., highlighting 544,
In some embodiments, the highlighting of the second type replaces at least a portion of the highlighting of the first type (812). For example, if a particular paragraph of text is already highlighted with yellow highlighting (e.g., highlighting 544,
In some embodiments, in response to detecting the movement of the initial contact on the touch-sensitive surface, in accordance with a determination that the initial location on the display is outside of the highlighted area, the device adds a new highlighted area to the document in accordance with the detected movement of the contact (814). In other words, when the predefined gesture is detected within a highlighted area, the device adds a second level of highlighting to at least a portion of the highlighted area, and in contrast, when the predefined gesture is detected outside of the highlighted area, the device adds highlighting to a portion of the document that is outside of the highlighted area. For example, gesture 562 (
In some embodiments, the new highlighted area is highlighted with the highlighting of the first type (816). In other words, in response to a particular type of gesture (e.g., tap and swipe), if the particular type of gesture is detected in an area that is already highlighted with a first type of highlighting, a second type of highlighting is added to at least a portion of the highlighted area. In contrast, if the particular type of gesture is detected in a respective area that is not already highlighted, the first type of highlighting is added to the respective area. For example, highlighting 568 and highlighting 544 (
In some embodiments, in response to detecting the movement of the initial contact on the touch-sensitive surface, in accordance with a determination that the initial location on the display is proximate to (e.g., within 10 pixels of or within 1 centimeters of) an edge of the highlighted area, the device adjusts the highlighted area in accordance with the detected movement instead of adding highlighting of the second type (818). In some embodiments, the highlighted area is only adjusted when the initial location on the display is outside of the highlighted area. In some embodiments, the highlighted area is adjusted without regard to whether or not the initial location on the display is within the highlighted area or outside of the highlighted area, so long as the initial location is proximate to the edge of the highlighted area. For example, gestures 554 and 558 are detected by device 100 in proximity of an edge of highlighting 544, as shown in
In some embodiments, in accordance with a determination that the detected movement corresponds to movement on the display towards the highlighted area, adjusting the highlighted area includes contracting the highlighted area (820). For example, gesture 554 (
In some embodiments, in accordance with a determination that the detected movement corresponds to movement on the display away from the highlighted area, adjusting the highlighted area includes expanding the highlighted area (822). For example, gesture 558 (
In accordance with some embodiments,
As shown in
In some embodiments, the first operational mode is a navigation-preferred mode; and the second operational mode is an annotation-preferred mode.
In some embodiments, while the electronic device is in a navigation-preferred mode: a plurality of simple gestures are associated with corresponding basic navigation operations; and a plurality of composite gestures are associated with corresponding basic annotation operations, where a composite gesture has multiple components including a single continuous contact on the touch-sensitive surface unit and at least one other component.
In some embodiments, while the electronic device is in an annotation-preferred mode: a plurality of simple gestures are associated with corresponding basic annotation operations; and a plurality of composite gestures are associated with corresponding basic navigation operations, where a composite gesture has multiple components including a single continuous contact on the touch-sensitive surface unit and at least one other component.
In some embodiments, the display unit 902 is displaying an electronic document, the first operation type is a navigation operation, and the second operation type is an annotation operation.
In some embodiments, the first gesture type is simpler to perform than the second gesture type.
In some embodiments, the first gesture type is a swipe gesture and the second gesture type is a tap and swipe gesture.
In some embodiments, the first gesture type is single contact gesture and the second gesture type is a multi-contact gesture.
In some embodiments, the operation performed at the electronic device 900 in response to detecting the first gesture is determined based at least in part on a location and/or direction of the first gesture on the touch-sensitive surface unit 904.
In some embodiments, the operation performed at the electronic device 900 in response to detecting the second gesture is determined based at least in part on a location and/or direction of the second gesture on the touch-sensitive surface unit 904.
In some embodiments, the electronic device 900 switches from the first operational mode to the second operational mode in response to detecting a predefined gesture.
In some embodiments, the electronic device 900 switches from the first operational mode to the second operational mode in response to detecting a finger drumming gesture on the touch-sensitive surface unit 904.
In some embodiments, the finger drumming gesture is a two-handed finger drumming gesture.
In some embodiments, the display unit 902 is distinct from the touch-sensitive surface unit 904 and the touch sensitive surface unit 904 is positioned on a side of the electronic device 900 that does not include the display unit 902.
In some embodiments, the processing unit 906 is configured to enable display of a graphical user interface element in response to switching from the first operational mode to the second operational mode (e.g., with a display enabling unit 912).
In accordance with some embodiments,
As shown in
In some embodiments, the predefined gesture is a finger drumming gesture.
In some embodiments, the touch-sensitive display unit 1002 is located on a first side of the electronic device 1000 and the touch-sensitive surface unit 1004 is located on a second side of the electronic device 1000 that is distinct from the first side.
In accordance with some embodiments,
As shown in
In some embodiments, the highlighting of the second type is coextensive with at least a portion of the highlighting of the first type.
In some embodiments, the highlighting of the second type replaces at least a portion of the highlighting of the first type.
In some embodiments, the processing unit 1106 is configured to, in response to detecting the movement of the initial contact on the touch-sensitive surface unit 1104, in accordance with a determination that the initial location on the display unit 1102 is outside of the highlighted area, add a new highlighted area to the document in accordance with the detected movement of the contact (e.g., with the adding unit 1110).
In some embodiments, the new highlighted area is highlighted with the first type.
In some embodiments, the processing unit 1106 is configured to, in response to detecting the movement of the initial contact on the touch-sensitive surface unit 1104, in accordance with a determination that the initial location on the display unit 1102 is proximate to an edge of the highlighted area, adjust the highlighted area in accordance with the detected movement instead of adding highlighting of the second type (e.g., with the adjusting unit 1112).
In some embodiments, in accordance with a determination that the detected movement corresponds to movement on the display unit 1102 towards the highlighted area, adjusting the highlighted area includes contracting the highlighted area; and in accordance with a determination that the detected movement corresponds to movement on the display unit 1102 away from the highlighted area, adjusting the highlighted area includes expanding the highlighted area.
The operations in the information processing methods described above may be implemented by running one or more functional modules in information processing apparatus such as general purpose processors or application specific chips. These modules, combinations of these modules, and/or their combination with general hardware (e.g., as described above with respect to
The operations described above with reference to
The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated.
This application claims priority to U.S. Provisional Application Ser. No. 61/435,776, filed Jan. 24, 2011, entitled “Device, Method, and Graphical User Interface for Navigating and Annotating an Electronic Document,” which is incorporated by reference herein in its entirety. This application is related to the following: (1) U.S. application Ser. No. 13/076,407, filed Mar. 30, 2011, entitled “Device, Method, and Graphical User Interface for Navigating and Annotating an Electronic Document,”; and (2) U.S. application Ser. No. 13/076,414, filed Mar. 30, 2011, entitled “Device, Method, and Graphical User Interface for Navigating and Annotating an Electronic Document,”, which are incorporated by reference herein in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 2794861 | Heine | Jun 1957 | A |
| 4081631 | Feder | Mar 1978 | A |
| 4107784 | Van Bemmelen | Aug 1978 | A |
| 4202041 | Kaplow et al. | May 1980 | A |
| 4204089 | Key et al. | May 1980 | A |
| 4313108 | Yoshida | Jan 1982 | A |
| 4332464 | Bartulis et al. | Jun 1982 | A |
| 4334219 | Paulus et al. | Jun 1982 | A |
| 4353056 | Tsikos | Oct 1982 | A |
| 4433377 | Eustis et al. | Feb 1984 | A |
| 4455452 | Schuyler | Jun 1984 | A |
| 4459581 | Wilson et al. | Jul 1984 | A |
| 4485439 | Rothstein | Nov 1984 | A |
| 4504133 | Nakai et al. | Mar 1985 | A |
| 4513379 | Wilson et al. | Apr 1985 | A |
| 4555775 | Pike | Nov 1985 | A |
| 4586158 | Brandle | Apr 1986 | A |
| 4598363 | Clark et al. | Jul 1986 | A |
| 4642790 | Minshull et al. | Feb 1987 | A |
| 4658425 | Julstrom | Apr 1987 | A |
| 4680429 | Murdock et al. | Jul 1987 | A |
| 4698625 | McCaskill et al. | Oct 1987 | A |
| 4746770 | McAvinney | May 1988 | A |
| 4755811 | Slavin et al. | Jul 1988 | A |
| 4790028 | Ramage | Dec 1988 | A |
| 4803463 | Sado | Feb 1989 | A |
| 4812831 | Laier | Mar 1989 | A |
| 5347295 | Agulnick et al. | Sep 1994 | A |
| 5729219 | Armstrong et al. | Mar 1998 | A |
| 5905497 | Vaughan et al. | May 1999 | A |
| 6037937 | Beaton et al. | Mar 2000 | A |
| 6154758 | Chiang | Nov 2000 | A |
| 6307549 | King et al. | Oct 2001 | B1 |
| 6486895 | Robertson et al. | Nov 2002 | B1 |
| 6657560 | Jung | Dec 2003 | B1 |
| 6842182 | Ungar et al. | Jan 2005 | B2 |
| 6924822 | Card et al. | Aug 2005 | B2 |
| 6944818 | Newman et al. | Sep 2005 | B2 |
| 6947062 | Cuijpers et al. | Sep 2005 | B2 |
| 6995746 | Aymeric | Feb 2006 | B2 |
| 7088342 | Rekimoto et al. | Aug 2006 | B2 |
| 7176888 | Marvit et al. | Feb 2007 | B2 |
| 7185274 | Rubin et al. | Feb 2007 | B1 |
| 7190349 | Kim et al. | Mar 2007 | B2 |
| 7299424 | Jarrett et al. | Nov 2007 | B2 |
| 7383517 | Baudisch et al. | Jun 2008 | B2 |
| 7434177 | Ording et al. | Oct 2008 | B1 |
| 7437683 | Beezer et al. | Oct 2008 | B1 |
| 7477231 | Asai | Jan 2009 | B2 |
| 7602378 | Kocienda et al. | Oct 2009 | B2 |
| 7614008 | Ording | Nov 2009 | B2 |
| 7634263 | Louch et al. | Dec 2009 | B2 |
| 7768501 | Maddalozzo, Jr. et al. | Aug 2010 | B1 |
| 8033744 | Baker | Oct 2011 | B2 |
| 8289162 | Mooring et al. | Oct 2012 | B2 |
| 8347232 | Prud'Hommeaux et al. | Jan 2013 | B1 |
| 8358321 | Weidner | Jan 2013 | B1 |
| 8365059 | Walsh et al. | Jan 2013 | B2 |
| 8368658 | Brisebois et al. | Feb 2013 | B2 |
| 8368723 | Gossweiler, III et al. | Feb 2013 | B1 |
| 8405630 | Bi et al. | Mar 2013 | B1 |
| 8448083 | Migos et al. | May 2013 | B1 |
| 8514186 | Tan | Aug 2013 | B2 |
| 8520025 | Patterson et al. | Aug 2013 | B2 |
| 8547354 | Koch et al. | Oct 2013 | B2 |
| 8619034 | Grad | Dec 2013 | B2 |
| 8659562 | Koch et al. | Feb 2014 | B2 |
| 8842082 | Migos et al. | Sep 2014 | B2 |
| 8850350 | Bi et al. | Sep 2014 | B2 |
| 8863020 | Hymel | Oct 2014 | B2 |
| 9013423 | Ferren | Apr 2015 | B2 |
| 9026932 | Dixon | May 2015 | B1 |
| 9047009 | King et al. | Jun 2015 | B2 |
| 9092132 | Migos et al. | Jul 2015 | B2 |
| 9104647 | Artin | Aug 2015 | B2 |
| 9113193 | Gardes et al. | Aug 2015 | B1 |
| 9117426 | Wieder | Aug 2015 | B2 |
| 9128614 | Koch et al. | Sep 2015 | B2 |
| 9146673 | Koch et al. | Sep 2015 | B2 |
| 9244604 | Lewbel | Jan 2016 | B1 |
| 9250798 | Migos et al. | Feb 2016 | B2 |
| 20020015064 | Robotham et al. | Feb 2002 | A1 |
| 20020028018 | Hawkins et al. | Mar 2002 | A1 |
| 20020105504 | Toepke et al. | Aug 2002 | A1 |
| 20020118175 | Liebenow et al. | Aug 2002 | A1 |
| 20030001899 | Partanen et al. | Jan 2003 | A1 |
| 20030184528 | Kawasaki et al. | Oct 2003 | A1 |
| 20030210272 | D'Souza | Nov 2003 | A1 |
| 20040021691 | Dostie et al. | Feb 2004 | A1 |
| 20040068409 | Tanaka et al. | Apr 2004 | A1 |
| 20040080487 | Griffin et al. | Apr 2004 | A1 |
| 20040100479 | Nakano et al. | May 2004 | A1 |
| 20040119750 | Harrison | Jun 2004 | A1 |
| 20040130575 | Tai et al. | Jul 2004 | A1 |
| 20040140984 | Hinckley et al. | Jul 2004 | A1 |
| 20040183834 | Chermesino | Sep 2004 | A1 |
| 20040201576 | Shimada et al. | Oct 2004 | A1 |
| 20040230912 | Clow et al. | Nov 2004 | A1 |
| 20050154798 | Nurmi | Jul 2005 | A1 |
| 20050225538 | Verhaegh | Oct 2005 | A1 |
| 20050248525 | Asai | Nov 2005 | A1 |
| 20060007178 | Davis | Jan 2006 | A1 |
| 20060033701 | Wilson | Feb 2006 | A1 |
| 20060033724 | Chaudhri et al. | Feb 2006 | A1 |
| 20060038796 | Hinckley et al. | Feb 2006 | A1 |
| 20060048072 | Jarrett et al. | Mar 2006 | A1 |
| 20060055685 | Rimas-Ribikauskas et al. | Mar 2006 | A1 |
| 20060061542 | Stokie | Mar 2006 | A1 |
| 20060080621 | Park | Apr 2006 | A1 |
| 20060085757 | Andre et al. | Apr 2006 | A1 |
| 20060150087 | Cronenberger et al. | Jul 2006 | A1 |
| 20060152389 | Kajikawa | Jul 2006 | A1 |
| 20060164399 | Cheston et al. | Jul 2006 | A1 |
| 20060181518 | Shen et al. | Aug 2006 | A1 |
| 20060197750 | Kerr et al. | Sep 2006 | A1 |
| 20060242607 | Hudson | Oct 2006 | A1 |
| 20060265648 | Rainisto et al. | Nov 2006 | A1 |
| 20070060228 | Akasaka et al. | Mar 2007 | A1 |
| 20070091070 | Larsen et al. | Apr 2007 | A1 |
| 20070097085 | Iwatsuki | May 2007 | A1 |
| 20070171210 | Chaudhri et al. | Jul 2007 | A1 |
| 20070273662 | Lian et al. | Nov 2007 | A1 |
| 20070277126 | Park et al. | Nov 2007 | A1 |
| 20080036743 | Westerman et al. | Feb 2008 | A1 |
| 20080042978 | Perez-Noguera | Feb 2008 | A1 |
| 20080082920 | Eom | Apr 2008 | A1 |
| 20080115078 | Girgaonkar | May 2008 | A1 |
| 20080134101 | Newman | Jun 2008 | A1 |
| 20080141126 | Johnson et al. | Jun 2008 | A1 |
| 20080158024 | Steiner et al. | Jul 2008 | A1 |
| 20080165141 | Christie | Jul 2008 | A1 |
| 20080165144 | Forstall et al. | Jul 2008 | A1 |
| 20080180408 | Forstall et al. | Jul 2008 | A1 |
| 20080198141 | Lee et al. | Aug 2008 | A1 |
| 20080259057 | Brons | Oct 2008 | A1 |
| 20080297377 | Wang et al. | Dec 2008 | A1 |
| 20090052778 | Edgecomb et al. | Feb 2009 | A1 |
| 20090058815 | Jeon et al. | Mar 2009 | A1 |
| 20090058820 | Hinckley | Mar 2009 | A1 |
| 20090058823 | Kocienda | Mar 2009 | A1 |
| 20090064047 | Shim et al. | Mar 2009 | A1 |
| 20090091541 | Chen | Apr 2009 | A1 |
| 20090122018 | Vymenets et al. | May 2009 | A1 |
| 20090132957 | Reddy | May 2009 | A1 |
| 20090140986 | Karkkainen et al. | Jun 2009 | A1 |
| 20090153288 | Hope et al. | Jun 2009 | A1 |
| 20090167706 | Tan et al. | Jul 2009 | A1 |
| 20090174669 | Shkolnikov | Jul 2009 | A1 |
| 20090174679 | Westerman | Jul 2009 | A1 |
| 20090189858 | Lev et al. | Jul 2009 | A1 |
| 20090195959 | Ladouceur et al. | Aug 2009 | A1 |
| 20090213081 | Case, Jr. | Aug 2009 | A1 |
| 20090225035 | Baik | Sep 2009 | A1 |
| 20090225041 | Kida et al. | Sep 2009 | A1 |
| 20090228842 | Westerman et al. | Sep 2009 | A1 |
| 20090231281 | Whytock et al. | Sep 2009 | A1 |
| 20090235281 | Lu et al. | Sep 2009 | A1 |
| 20090237359 | Kim et al. | Sep 2009 | A1 |
| 20090237361 | Mosby et al. | Sep 2009 | A1 |
| 20090241054 | Hendricks | Sep 2009 | A1 |
| 20090243898 | Iorfida et al. | Oct 2009 | A1 |
| 20090244020 | Sjolin | Oct 2009 | A1 |
| 20090247233 | Kim | Oct 2009 | A1 |
| 20090251422 | Wu et al. | Oct 2009 | A1 |
| 20090256817 | Perlin et al. | Oct 2009 | A1 |
| 20090258677 | Ellis et al. | Oct 2009 | A1 |
| 20090265627 | Kim et al. | Oct 2009 | A1 |
| 20090267906 | Schroderus | Oct 2009 | A1 |
| 20090273566 | Lu et al. | Nov 2009 | A1 |
| 20090303200 | Grad | Dec 2009 | A1 |
| 20090309768 | Pihlaja | Dec 2009 | A1 |
| 20100004029 | Kim | Jan 2010 | A1 |
| 20100020033 | Nwosu | Jan 2010 | A1 |
| 20100020034 | Kim | Jan 2010 | A1 |
| 20100058212 | Belitz et al. | Mar 2010 | A1 |
| 20100064261 | Andrews et al. | Mar 2010 | A1 |
| 20100070613 | Chen et al. | Mar 2010 | A1 |
| 20100088641 | Choi | Apr 2010 | A1 |
| 20100103124 | Kruzeniski et al. | Apr 2010 | A1 |
| 20100105408 | Palmer et al. | Apr 2010 | A1 |
| 20100107050 | Wang et al. | Apr 2010 | A1 |
| 20100110017 | Lee | May 2010 | A1 |
| 20100141590 | Markiewicz et al. | Jun 2010 | A1 |
| 20100146459 | Repka | Jun 2010 | A1 |
| 20100153313 | Baldwin et al. | Jun 2010 | A1 |
| 20100156793 | Ozias et al. | Jun 2010 | A1 |
| 20100164959 | Brown et al. | Jul 2010 | A1 |
| 20100185949 | Jaeger | Jul 2010 | A1 |
| 20100194692 | Orr et al. | Aug 2010 | A1 |
| 20100214237 | Echeverri et al. | Aug 2010 | A1 |
| 20100231612 | Chaudhri et al. | Sep 2010 | A1 |
| 20100235726 | Ording et al. | Sep 2010 | A1 |
| 20100235794 | Ording | Sep 2010 | A1 |
| 20100238125 | Ronkainen | Sep 2010 | A1 |
| 20100238139 | Goertz et al. | Sep 2010 | A1 |
| 20100241985 | Kim et al. | Sep 2010 | A1 |
| 20100259484 | Jo | Oct 2010 | A1 |
| 20100259493 | Chang et al. | Oct 2010 | A1 |
| 20100259561 | Forutanpour et al. | Oct 2010 | A1 |
| 20100259562 | Miyazawa et al. | Oct 2010 | A1 |
| 20100277414 | Tartz et al. | Nov 2010 | A1 |
| 20100283743 | Coddington | Nov 2010 | A1 |
| 20100289756 | Anzures et al. | Nov 2010 | A1 |
| 20100293498 | Maxfield | Nov 2010 | A1 |
| 20100295781 | Alameh et al. | Nov 2010 | A1 |
| 20100299597 | Shin et al. | Nov 2010 | A1 |
| 20100302155 | Sands et al. | Dec 2010 | A1 |
| 20100306363 | Saputra et al. | Dec 2010 | A1 |
| 20100315359 | Seong et al. | Dec 2010 | A1 |
| 20110006996 | Smith et al. | Jan 2011 | A1 |
| 20110007009 | Ishihara et al. | Jan 2011 | A1 |
| 20110009169 | Kim | Jan 2011 | A1 |
| 20110029918 | Yoo et al. | Feb 2011 | A1 |
| 20110039602 | McNamara et al. | Feb 2011 | A1 |
| 20110050607 | Park | Mar 2011 | A1 |
| 20110055753 | Horodezky et al. | Mar 2011 | A1 |
| 20110074699 | Marr et al. | Mar 2011 | A1 |
| 20110078560 | Weeldreyer et al. | Mar 2011 | A1 |
| 20110078614 | Lee et al. | Mar 2011 | A1 |
| 20110106439 | Huang et al. | May 2011 | A1 |
| 20110179387 | Shaffer et al. | Jul 2011 | A1 |
| 20110187647 | Woloszynski et al. | Aug 2011 | A1 |
| 20110191718 | Hinckley et al. | Aug 2011 | A1 |
| 20110191719 | Hinckley et al. | Aug 2011 | A1 |
| 20110199393 | Nurse et al. | Aug 2011 | A1 |
| 20110202877 | Lassonde et al. | Aug 2011 | A1 |
| 20110221684 | Rydenhag | Sep 2011 | A1 |
| 20110231796 | Vigil | Sep 2011 | A1 |
| 20110242138 | Tribble | Oct 2011 | A1 |
| 20110258537 | Rives et al. | Oct 2011 | A1 |
| 20110263298 | Park | Oct 2011 | A1 |
| 20110302532 | Missig | Dec 2011 | A1 |
| 20120046947 | Fleizach | Feb 2012 | A1 |
| 20120096345 | Ho et al. | Apr 2012 | A1 |
| 20120110431 | Rosenfeld et al. | May 2012 | A1 |
| 20120112024 | Gõtzl | May 2012 | A1 |
| 20120112025 | Smeenk | May 2012 | A1 |
| 20120112026 | Crawford | May 2012 | A1 |
| 20120113007 | Koch et al. | May 2012 | A1 |
| 20120113023 | Koch et al. | May 2012 | A1 |
| 20120113024 | Koch et al. | May 2012 | A1 |
| 20120113025 | Koch et al. | May 2012 | A1 |
| 20120113026 | Koch | May 2012 | A1 |
| 20120113126 | Koch et al. | May 2012 | A1 |
| 20120117501 | Koch et al. | May 2012 | A1 |
| 20120117505 | Koch et al. | May 2012 | A1 |
| 20120117506 | Koch et al. | May 2012 | A1 |
| 20120120016 | Mittal et al. | May 2012 | A1 |
| 20120127206 | Thompson et al. | May 2012 | A1 |
| 20120139844 | Ramstein et al. | Jun 2012 | A1 |
| 20120162078 | Ferren et al. | Jun 2012 | A1 |
| 20120188174 | Migos et al. | Jul 2012 | A1 |
| 20120192065 | Migos et al. | Jul 2012 | A1 |
| 20120192093 | Migos et al. | Jul 2012 | A1 |
| 20120206363 | Kyprianou et al. | Aug 2012 | A1 |
| 20120206370 | Ivanovic | Aug 2012 | A1 |
| 20120324381 | Cohen et al. | Dec 2012 | A1 |
| 20130002565 | Tumanov et al. | Jan 2013 | A1 |
| 20130016129 | Gossweiler, III et al. | Jan 2013 | A1 |
| 20130055140 | Mosquera et al. | Feb 2013 | A1 |
| 20130057475 | Duggan et al. | Mar 2013 | A1 |
| 20130067382 | Townsend et al. | Mar 2013 | A1 |
| 20130167013 | Poliak | Jun 2013 | A1 |
| 20130222244 | Mak et al. | Aug 2013 | A1 |
| 20130234949 | Chornenky | Sep 2013 | A1 |
| 20130265225 | Nasiri et al. | Oct 2013 | A1 |
| 20130286435 | Anezaki et al. | Oct 2013 | A1 |
| 20130311867 | Patterson et al. | Nov 2013 | A1 |
| 20140006994 | Koch et al. | Jan 2014 | A1 |
| 20140040835 | Hildreth et al. | Feb 2014 | A1 |
| 20140223381 | Huang et al. | Aug 2014 | A1 |
| 20140351691 | Neil et al. | Nov 2014 | A1 |
| 20150235370 | Abovitz et al. | Aug 2015 | A1 |
| 20160147438 | Migos et al. | May 2016 | A1 |
| 20180004408 | Booking et al. | Jan 2018 | A1 |
| Number | Date | Country |
|---|---|---|
| 1666170 | Sep 2005 | CN |
| 1668994 | Sep 2005 | CN |
| 1280700 | Oct 2006 | CN |
| 1307518 | Mar 2007 | CN |
| 0422577 | Apr 1991 | EP |
| 1 536 316 | Jun 2005 | EP |
| 1 703 363 | Sep 2006 | EP |
| 1791051 | May 2007 | EP |
| 2 105 823 | Sep 2009 | EP |
| 2 109 031 | Oct 2009 | EP |
| 2 133 778 | Dec 2009 | EP |
| 2 341 414 | Jul 2011 | EP |
| 2 402 105 | Dec 2004 | GB |
| 2001-356870 | Dec 2001 | JP |
| 2002-508559 | Mar 2002 | JP |
| 2002-244780 | Aug 2002 | JP |
| 2005 244301 | Sep 2005 | JP |
| 2005-526303 | Sep 2005 | JP |
| 2005-531861 | Oct 2005 | JP |
| 2005-310039 | Nov 2005 | JP |
| 2006-139397 | Jun 2006 | JP |
| 2007-183787 | Jul 2007 | JP |
| 2007 279638 | Oct 2007 | JP |
| 2009-509235 | Mar 2009 | JP |
| 2009-527041 | Jul 2009 | JP |
| 2010-134755 | Jun 2010 | JP |
| 2010-179662 | Aug 2010 | JP |
| 10-2005-0016691 | Feb 2005 | KR |
| 10-2009-0101741 | Sep 2009 | KR |
| 10-0975168 | Aug 2010 | KR |
| 200928943 | Jul 2009 | TW |
| 199931571 | Jun 1999 | WO |
| 200068771 | Nov 2000 | WO |
| WO 0074240 | Dec 2000 | WO |
| WO 0215211 | Feb 2002 | WO |
| 2003036795 | May 2003 | WO |
| WO 03062978 | Jul 2003 | WO |
| WO 04006080 | Jan 2004 | WO |
| WO 05033856 | Apr 2005 | WO |
| WO 05076477 | Aug 2005 | WO |
| WO 07014064 | Feb 2007 | WO |
| 2007093984 | Aug 2007 | WO |
| WO 07089766 | Aug 2007 | WO |
| WO 09049331 | Apr 2009 | WO |
| 2009084147 | Jul 2009 | WO |
| WO 10018579 | Feb 2010 | WO |
| WO 10089740 | Aug 2010 | WO |
| 2010110550 | Sep 2010 | WO |
| 2010117374 | Oct 2010 | WO |
| WO 11123099 | Oct 2011 | WO |
| WO 2012083499 | Jun 2012 | WO |
| Entry |
|---|
| Ajidev, “iAnnotate,” ajidev.com. 2010, www.ajidev.com/iannotate, 2 pages. |
| Ajidev, “Welcome to iAnnotate v 1.3!” Ajidev.com. 2010, www.ajidev.com, 37 pages. |
| Chen et al., “Navigation Techniques for Dual-Display E-Book Readers,” CHI 2008 Proceedings, Apr. 2008, Florence, Italy, 10 pages. |
| Find eBook Readers, “PDF on the iPad-iAnnotate Revew-Annotations!” Find eBook Readers Blog, May 2010, http://findebookreaders.com/blog/2010/05/pdf-on-the-ipad-iannotate-review-annotations/, 9 pages. |
| Goodiware, “GoodReader User Manual; Viewing PDF Files,” goodíware.com, 2010, http://www.goodreader.net/gr-man-view-pdf.html#annots, 11 pages. |
| Lee et al., “smartNote for iPad User Guide,” mysmartnote.net; Version 1.4, 2010, http://mysmartnet.net, 17 pages. |
| Mobipocket “Mobipocket Reader Desktop 6.2,” Mobipocket .com, 2010, http://www.mobipocket.com/en/downloadsoft/productdetailsreader.asp, 3 pages. |
| Readdle Inc., “PDF Expert for iPad User's Guide.” Readdle Inc., 2010, 15 pages. |
| Vimeo, “Smart Design magazine UX concept,” vimeo.com, 2010, http://vimeo.com/10813230, 2 pages. |
| Willems et al., “Pen gestures in online map and photograph annotation tasks,” Oct. 2006, 6 pages. |
| International Search Report and Written Opinion dated May 23, 2011, recieved in International Application No. PCT/US2011/029957, which corresponds to U.S. Appl. No. 12/752,003, 11 pages (Tribble). |
| Dutch Search Report and Written Opinion dated May 4, 2012, received in Dutch Patent Application No. 2007721, which corresponds to U.S. Appl. No. 13/076,389, 16 pages (Koch). |
| International Search Report and Written Opinion dated May 7, 2012, received in Internatioanl Application No. PCT/US2011/059085, which corresponds to U.S. Appl. No. 10/076,389, 17 pages (Koch). |
| Dutch Search Report and Written Opinion dated May 4, 2012, received in Dutch Patent Application No. 2007723, which corresponds to U.S. Appl. No. 13/076,392, 10 pages (Koch). |
| International Search Report and Written Opinion dated May 7, 2012, received in International Application No. PCT/US2011/059088, which corresponds to U.S. Appl. No. 13/076,392, 12 pages (Koch). |
| Invitation to Pay Additional Fees dated May 23, 2012, received in International Patent Application No. PCT/US2011/059092, which corresponds to U.S. Appl. No. 13/076,395, 9 pages (Koch). |
| International Search Report and Written Opinion dated Feb. 11, 2013, received in International Application No. PCT/US2011/059092, which corresponds to U.S. Appl. No. 13/076,395, 35 pages (Koch). |
| International Search Report and Written Opinion dated May 7, 2012, received in International Application No. PCT/US2011/059101, which corresponds to U.S. Appl. No. 13/076,393, 12 pages (Koch). |
| International Search Report and Written Opinion dated May 7, 2012, recieved in International Application No. PCT/US2011/059106, which corresponds to U.S. Appl. No. 13/076,391, 13 pages (Koch). |
| Dutch Search Report and Written Opinion dated May 4, 2012, received in Dutch Patent Application No. 2007722, which corresponds to U.S. Appl. No. 13/243,599, 10 pages (Koch). |
| International Search Report and Written Opinion dated May 7, 2012, received in International Application No. PCT/US2011/059204, which corresponds to U.S. Appl. No. 13/243,599, 10 pages (Koch). |
| Office Action dated Feb. 22, 2013, received in U.S. Appl. No. 12/752,003, 39 pages (Tribble). |
| Office Action dated Oct. 3, 2012, received in U.S. Appl. No. 13/076,389, 11 pages (Koch). |
| Office Action dated Dec. 13, 2012, received in U.S. Appl. No. 13/076,395, 17 pages (Koch). |
| Office Action dated Dec. 14, 2012, received in U.S. Appl. No. 13/076,397, 20 pages (Koch). |
| Office Action dated Feb. 12, 2013, received in U.S. Appl. No. 13/076,399, 28 pages (Koch). |
| Office Action dated Dec. 17, 2012, received in U.S. Appl. No. 13/076,401, 16 pages (Koch). |
| Office Acton dated Nov. 9, 2012, received in U.S. Appl. No. 13/077,754, 9 pages (Migos). |
| Office Action dated Nov. 2, 2012, received in U.S. Appl. No. 13/076,393, 8 pages (Koch). |
| Office Action dated Jan. 17, 2013 received in U.S. Appl. No. 13/243,599, 17 pages (Koch). |
| Blind Type, “Touch typing the way it should be,” 2010, 2 pages. |
| Concept Phones, “Apple Tablet,” Concept Phones.com, Dec. 16, 2009, http://www.concept-phones.com/?s=apple+tablet, 21 pages. |
| G.P. Imports, “Keyboard Upgrade,” G.P. Imports, Inc. , updated May 20, 2010, 8 pages. |
| Gizmodo, “How Will Type on the Apple Tablet?”, Gizmodo.com, Jan. 12, 2010, http://gizmodo.com/5446652/how-will-we-type-on-the-apple-tablet, 5 pages. |
| Robbin, S., “Concept: iPad Split Keyboard,” Jan. 27, 2010, http://srobbin.com/blog/concept-ipad-split-keyboard/, 3 pages. |
| Surur, “Microsoft patents cool multi-touch virtual keyboard,” wmpoweruser.com, Sep. 25, 2009, http://wmpoweruser.com/microsoft-patents-cool-multi-touch-virtual-keyboard/. |
| Tidwell, J., “Magnetism,” from Designing Interfaces, Copyright © 2006 O'Reilly Media, Inc., pp. 279-280. |
| Toshiba, “Libertto® W100,” Jun. 2010, 9 pages. |
| Dutch Search Report dated May 23, 2012, recieved in Dutch Patent Application No. 2007725, which corresponds to U.S. Appl. No. 13/076,395, 12 pages (Koch). |
| Dutch Search Report dated May 14, 2012, recieved in Dutch Patent Application No. 2007719, which corresponds to U.S. Appl. No. 13/076,393, 10 pages (Koch). |
| Dutch Search Report dated May 14, 2012, recieved in Dutch Patent Application No. 2007718, which corresponds to U.S. Appl. No. 13/076,391, 10 pages ( Koch). |
| Office Action dated Nov. 2, 2012, recieved in U.S. Appl. No. 13/076,392, 9 pages (Koch). |
| Guimbretiêre, F., “Paper Augmented Digital Documents,” UIST '03, Nov. 2003, Vancouver, BC, Canada, 10 pages. |
| International Preliminary Report on Patentability dated May 16, 2013, recieved in International Application No. PCT/US2011/059085, which corresponds to U.S. Appl. No. 13/076,389, 10 pages (Koch). |
| International Preliminary Report on Patentability dated May 16, 2013, received in Interntaional Application No. PCT/US2011/059088, which corresponds to U.S. Appl. No. 13/076,392, 10 pages (Koch). |
| International Preliminary Report on Patentability dated Jul. 4, 2013, received in International Patent Application No. PCT/US2011/059092, which corresponds to U.S. Appl. No. 13/076,395, 16 pages (Koch). |
| International Preliminary Report on Patentability dated May 16, 2013, received in International Application No. PCT/US2011/059101, which corresponds to U.S. Appl. No. PCT/US2011/059101, 10 pages (Koch). |
| International Preliminary Report on Patentability dated May 16, 2013, received in International Patent No. PCT/US2011/059106, which corresponds to U.S. Appl. No. 13/076,391, 10 pages (Koch). |
| International Preliminary Report on Patentability dated May 16, 2013, received in International Application No. PCT/US2011/059204, which corresponds to U.S. Appl. No. 13/243,599, 8 pages (Koch). |
| International Search Report and Written Opinion dated Jul. 24, 2013, received in International Application No. PCT/US2013/037423, which corresponds to U.S. Appl. No. 13/797,979, 11 pages (Koch). |
| Notice of Allowance dated May 2, 2013, received in U.S. Appl. No. 13/076,389, 9 pages (Koch). |
| Notice of Allowance dated May 28, 2013, received in U.S. Appl. No. 13/076,389, 10 pages (Koch). |
| Notice of Allowance dated Aug. 6, 2013 received in U.S. Appl. No. 13/076,392, 14 pages (Koch). |
| Notice of Allowance dated Jul. 18, 2013, received in U.S. Appl. No. 13/076,401, 10 pages (Koch). |
| Office Action dated Aug. 21, 2013, received in U.S. Appl. No. 13/076,414, 14 pages (Migos). |
| Office Action dated Jul. 15, 2013, received in U.S. Appl. No. 13/077,754, 17 pages (Migos). |
| Office Action dated Feb. 7, 2013, received in U.S. Appl. No. 13/076,391, 20 pages (Koch). |
| “HTC Europe Co. Ltd and Apple Inc. Invalidity Claim No. HC 12 C 01465, together with annexes”, Apr. 5, 2012, 12 pages. |
| “HTC Europe Co. Ltd and Apple Inc. invalidity Claim No. HC11 C02703 together with amended Particulars of Claim and amended Grounds of invalidity”, Jul. 29, 2011, 22 pages. |
| “Motorola Mobility Opposition Grounds to Apple Inc. European Patent EP 2126678 dated Apr. 11, 2012, together with Exhibits E3, E4, and E5 re: CHT 2005, Apr. 2-7, 2005, Portland Oregon, USA”, Apr. 2012, 53 pages. |
| “Pleading notes Mr B.J. Berghuis van Woortman, in matter of Apple Inc. vs Samsung Electronics, Case No. KG ZA 11-730 and KG ZA 11-731”, Aug. 10-11, 2010, pp. 1-16. |
| “Pleading notes Mr Kleemans, Mr Blomme and Mr Van Oorschot, in matter of Apple Inc. vs Samsung Electronics, Case No. KG ZA 11-730 and KG ZA 11-731”, Aug. 10, 2011, 35 pages. |
| “The Textbook of the Future”, Nature, vol. 458, Apr. 2, 2009, pp. 568-570. |
| Apple Inc. vs. Samsung Electronics Co. Ltd., “Judgment in Interlocutory proceeding”, Case No. 396957/KG ZA 11-730, civil law sector, Aug. 24, 2011, pp. 1-65. |
| Apple Inc. vs. Samsung Electronics Co. Ltd., “Samsung's Motion to Supplement Invalidity Contentions”, Case No. 11-cv-01846-LHK, 2012 together with Exhibit 6, Jan. 27, 2012, 47 pages. |
| Apple Inc. vs. Samsung Electronics Co. Ltd., “Samsung's Patent Local Rule 3-3 and 3-4 Disclosures”, Case No. 11-cv-01846-LHK, together with Exhibits G-1 through G-7 and Exhibit H, Oct. 7, 2011, 287 pages. |
| crackberry.com, “Quick Way to Hide Keyboard?”, available at <http://forums.crackberry.com/f86/quick-way-hide-keyboard-103108/>, Nov. 26, 2008, 6 pages. |
| Decision to Grant received for European Patent Application No. 11784558.6, dated Sep. 22, 2016, 3 pages. |
| Decision to Grant received for European Patent Application No. 11784560.2, dated Jan. 5, 2018, 3 pages. |
| Final Office Action received for U.S. Appl. No. 12/752,003, dated Jun. 11, 2013, 40 pages. |
| Final Office Action received for U.S. Appl. No. 12/752,003, dated Sep. 26, 2014, 40 pages. |
| Final Office Action received for U.S. Appl. No. 13/076,414, dated Feb. 19, 2014, 10 pages. |
| Final Office Action received for U.S. Appl. No. 13/077,754 dated Jan. 14, 2015, 16 pages. |
| Final Office Action received for U.S. Appl. No. 13/797,979, dated May 8, 2015, 26 pages. |
| Grossman et al., “The Bubble Cursor: Enhancing Target Acquisition by Dynamic Resizing of the Cursor's Activation Area”, PAPERS: Smart Interaction Techniques 1, Apr. 2-7, 2005, pp. 281-290. |
| Gutwin et al., “Improving Interpretation of Remote Gestures with Telepointer Traces”, In Proceedings of the 2002 ACM Conference on Computer Supported Cooperative Work, Nov. 16-20, 2002, pp. 49-57. |
| Hertzum et al., “Input Techniques that Dynamically Change their Cursor Activation Area: A Comparison of Bubble and Cell Cursors”, International Journal of Human-Computer Studies, vol. 65, No. 10, Oct. 2007, 38 pages. |
| HTC Corporation, “DROID ERIS User Guide”, available at <http://member.america.htc.com/download/Web_materials/Manual/DOID_ERIS_ Verizon/DROID_ERIS_Verizon_English_UM_11_5.pdf>, 2009, 238 pages. |
| Intention to Grant received for Denmark Patent Application No. 11784562.8, dated Aug. 31, 2017, 8 pages. |
| Intention to Grant received for European Patent Application No. 11784558.6, dated May 4, 2016, 6 pages. |
| Intention to Grant received for European Patent Application No. 11784560.2, dated Aug. 9, 2017, 7 pages. |
| Intention to Grant received for European Patent Application No. 11784560.2, dated May 6, 2016, 6 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2011/029957, dated Oct. 11, 2012, 8 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2013/037423, dated Dec. 31, 2014, 7 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2010/020263, dated Dec. 8, 2010, 11 pages. |
| Liao et al., “PACER: Fine-grained Interactive Paper via Camera-touch Hybrid Gestures on a Cell Phone”, CHI 2010, ACM, Apr. 10-15, 2010, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/752,003, dated Mar. 7, 2014, 64 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/752,003, dated Sep. 19, 2013, 49 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/788,283, dated May 11, 2012, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/788,283, dated Oct. 12, 2012, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/794,625, dated Oct. 26, 2012, 7 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/076,391, dated Jul. 16, 2014, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/076,391, dated Nov. 7, 2013, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/076,395, dated Jul. 17, 2014, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/076,395, dated Oct. 23, 2013, 7 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/076,407, dated Dec. 5, 2013, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/077,711, dated Apr. 25, 2014, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/077,754, dated Mar. 21, 2014, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/797,979, dated Jan. 16, 2015, 26 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/083,349, dated May 27, 2014, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/012,178, dated Sep. 8, 2017, 11 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2011323301, dated Jan. 21, 2016, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2011323375, dated Jan. 22, 2016, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2011323269, dated Apr. 16, 2015, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201180026541.6, dated Sep. 8, 2016, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 201180059559.6, dated Aug. 1, 2017, 2 Pages (Official Copy only). {See communication under 37 CFR § 1.98(a) (3)}. |
| Notice of Allowance received for Chinese Patent Application No. 201180059590.X, dated Sep. 7, 2016, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2014-261158, dated Dec. 18, 2015, 6 pages (3 pages of English Translation and 3 pages of official copy). |
| Notice of Allowance received for Japanese Patent Application No. 2013-524269, dated Jan. 26, 2015, 3 pages (Official Copy only). {See communication under 37 CFR § 1.98(a) (3)}. |
| Notice of Allowance received for Japanese Patent Application No. 2013-537812, dated Dec. 5, 2014, 3 pages (Official Copy only). {See communication under 37 CFR § 1.98(a) (3)}. |
| Notice of Allowance received for Japanese Patent Application No. 2013-537813, dated Sep. 29, 2014, 3 pages (Official Copy only). {See communication under 37 CFR § 1.98(a) (3)}. |
| Notice of Allowance received for Japanese Patent Application No. 2016-006518, dated Mar. 17, 2017, 3 pages (Official Copy Only). {See communication under 37 CFR § 1.98(a) (3)}. |
| Notice of Allowance received for Korean Patent Application No. 10-2012-7030352, dated Dec. 11, 2017, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2013-7013933, dated Feb. 26, 2015, 2 pages (Official Copy only). {See communication under 37 CFR § 1.98(a) (3)}. |
| Notice of Allowance received for Korean Patent Application No. 10-2013-7014110, dated Jan. 28, 2015, 2 pages (Official Copy only). {See communication under 37 CFR § 1.98(a) (3)}. |
| Notice of Allowance received for Korean Patent Application No. 10-2014-7015535, dated Dec. 6, 2017, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 12/788,283, dated May 9, 2013, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 12/788,283, dated Sep. 16, 2013, 16 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/076,391, dated Jan. 29, 2015, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/076,391, dated Jun. 17, 2015, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/076,393, dated Oct. 3, 2013, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/076,395, dated Jan. 30, 2015, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/076,395, dated May 18, 2015, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/076,397, dated Nov. 26, 2013, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/076,397, dated Sep. 16, 2013, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/076,399, dated Oct. 10, 2013, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/076,407, dated May 20, 2014, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/076,414, dated Aug. 26, 2015, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/076,414, dated May 4, 2016, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/077,711, dated Mar. 23, 2015, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/077,711, dated Nov. 28, 2014, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/077,754, dated Sep. 18, 2015, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/243,599, dated Aug. 6, 2013, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/083,349, dated Apr. 29, 2015, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/083,349, dated Jan. 23, 2015, 9 pages. |
| Office Action received for Australian Patent Application No. 2011323269, dated Aug. 5, 2013, 3 pages. |
| Office Action received for Australian Patent Application No. 2011323269, dated Sep. 3, 2014, 3 pages. |
| Office Action received for Australian Patent Application No. 2011323301, dated Nov. 12, 2014, 3 pages. |
| Office Action received for Australian Patent Application No. 2011323375, dated Nov. 12, 2014, Nov. 12, 2014, 4 pages. |
| Office Action received for Australian Patent Application No. 2016202878, dated Apr. 12, 2017, 4 pages. |
| Office Action received for Chinese Patent Application No. 201080001777.x, dated Jan. 28, 2013, 12 pages (English Translation only). |
| Office Action received for Chinese Patent Application No. 201080001777.x, dated Nov. 13, 2013, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201180026541.6, dated Jul. 16, 2015, 10 pages (3 pages of English Translation and 7 pages of Official Copy). |
| Office Action Received for Chinese Patent Application No. 201180026541.6, dated Mar. 21, 2016, 8 pages (3 pages of English Translation and 5 pages of Official Copy). |
| Office Action Received for Chinese Patent Application No. 201180059559.6, dated Apr. 27, 2017, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201180059559.6, dated May 9, 2016, 16 pages (4 pages of English Translation and 12 pages of Official Copy). |
| Office Action Received for Chinese Patent Application No. 201180059559.6, dated Nov. 1, 2016, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action Received for Chinese Patent Application No. 201180059559.6, dated Sep. 11, 2015, 28 pages (19 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201180059590.X, dated Apr. 13, 2016, 4 pages (1 page of English Translation and 3 pages of Official copy). |
| Office Action Received for Chinese Patent Application No. 201180059590.X, dated Aug. 4, 2015, 15 pages (7 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for European Patent Application No. 10700014.3, dated Aug. 29, 2013, Aug. 29, 2013, 6 pages. |
| Office Action received for European Patent Application No. 11784558.6, dated Jun. 23, 2014, 5 pages. |
| Office Action received for European Patent Application No. 11784560.2, dated Jun. 23, 2014, 5 pages. |
| Office Action received for European Patent Application No. 11784562.8, dated Feb. 21, 2014, 5 pages. |
| Office Action Received for European Patent Application No. 11784562.8, dated Nov. 30, 2015, 6 pages. |
| Office Action received for Japanese Patent Application No. 2012-547987, dated Nov. 22, 2013, 5 pages (2 pages of English Translation and 3 pages of official copy). |
| Office Action received for Japanese Patent Application No. 2013-524269, dated Jul. 7, 2014, 5 pages (3 pages of English Translation and 2 pages of Official copy). |
| Office Action received for Japanese Patent Application No. 2013-537812, dated Mar. 7, 2014, 7 pages (4 pages of English translation and 3 pages of Official copy). |
| Office Action received for Japanese Patent Application No. 2013-537813, dated Apr. 4, 2014, 6 pages (4 pages of English Translation and 2 pages of Office Copy). |
| Office Action received for Japanese Patent Application No. 2013-537813, dated Aug. 8, 2014, 4 pages (2 pages of English Translation and 2 pages of Official copy). |
| Office Action received for Japanese Patent Application No. 2016006518, dated Nov. 21, 2016, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2012-7020604, dated Oct. 11, 2013, 4 pages (1 page of English Translation and 3 pages of Official copy). |
| Office Action received for Korean Patent Application No. 10-2012-7030352, dated Dec. 24, 2015, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2012-7030352, dated Dec. 9, 2013, 7 pages (3 pages of English Translation and 4 pages of Official copy). |
| Office Action received for Korean Patent Application No. 10-2012-7030352, dated Feb. 23, 2015, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2012-7030352, dated Oct. 24, 2014, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2013-7013933, dated Mar. 26, 2014, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2013-7014110, dated Mar. 26, 2014, 7 pages (3 pages of English Translation and 4 pages of Official copy). |
| Office Action received for Korean Patent Application No. 1020147015535, dated Jan. 19, 2017, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2014-7015535, dated Jul. 31, 2017, 7 pages (3 pages of English translation and 4 pages of Official Copy). |
| Ren et al., “The Adaptive Hybrid Cursor: A Pressure-Based Target Selection Technique for Pen-Based User interfaces”, INTERACT '07, Proceedings of the 11th IFIP TC 13 International Conference on Human-Computer Interaction, Sep. 10, 2007, 14 pages. |
| Samsung Electronics GmbH vs Apple Inc., “List scrolling and document translation, scaling and rotation on a touch-screen display”, Opposition, Jan. 30, 2012, 27 pages. |
| Samsung Electronics vs Apple Inc., “Statement of Defense Also Counterclaim, Case No. KG ZA 2011-730”, Jul. 20, 2011, 44 pages. |
| Samsung Electronics vs Apple Inc., “Statement of Defense Also Counterclaim, Case No. KG ZA 2011-731”, Jul. 20, 2011, 48 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 11784560.2, dated Oct. 18, 2016, 8 pages. |
| Wang et al., “Detecting and Leveraging Finger Orientation for Interaction with Direct-Touch Surfaces”, ACM, Oct. 4-7, 2009, pp. 23-32. |
| Wilson, Andrew D., “TouchLight: An Imaging Touch Screen and Display for Gesture-Based Interaction”, ACM, Oct. 13-15, 2004, 8 pages. |
| Wu et al., “Gesture Registration, Relaxation, and Reuse for Multi-Point Direct-Touch Surfaces”, Proceedings of the First IEEE International Workshop on Horizontal Interactive Human-Computer Systems, 2006, 8 pages. |
| XDA-Developers, “FingerKeyboard2.1”, available at <http://forum.xda-developers.com/showthread.php?t=487677>, retrieved on Apr. 16, 2013, 7 pages. |
| Decision to Grant received for European Patent Application No. 11784562.8, dated Jan. 18, 2018, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2016202878, dated Mar. 28, 2018, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/012,178, dated Apr. 5, 2018, 6 pages. |
| Kahol et al., “Documenting Motion Sequences with a Personalized Annotation”, IEEE, 2006, pp. 37-45. |
| Liao et al., “PapierCraft: A Gesture-Based Command System for Interactive Paper”, ACM, 2008, 31 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20120192093 A1 | Jul 2012 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61435776 | Jan 2011 | US |
