Application programming interfaces for scrolling operations

Description

FIELD OF THE INVENTION

This disclosure relates to application programming interfaces that provide scrolling operations.

Computer Program Listing

A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent & Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

Applicant has submitted herewith Computer Program Listings which are included as Appendix A, attached.

BACKGROUND OF THE INVENTION

An API is a source code interface that a computer system or program library provides in order to support requests for services from a software application. An API is specified in terms of a programming language that can be interpretative or compiled when an application is built, rather than an explicit low level description of how data is laid out in memory. The software that provides the functionality described by an API is said to be an implementation of the APL

Various devices such as electronic devices, computing systems, portable devices, and handheld devices have software applications. The API interfaces between the software applications and user interface software to provide a user of the device with certain features and operations. A user may desire certain operations such as scrolling, selecting, gesturing, and animating operations for a display of the device.

Scrolling is the act of sliding a directional (e.g., horizontal or vertical) presentation of content, such as text, drawings, or images, across a screen or display window. In a typical graphical user interface, scrolling is done with the help of a scrollbar or using keyboard shortcuts, often the arrow keys. Gesturing is a type of user input with two or more input points. Animating operations include changing content within a given time period.

The various types of devices may have a limited display size, user interface, software, API interface and/or processing capability which limits the ease of use of the devices. User interfaces of devices implement APIs in order to provide requested functionality and features. These user interfaces can have difficulty interpreting the various types of user inputs and providing the intended functionality associated with the user inputs.

SUMMARY OF THE INVENTION

At least certain embodiments of the present disclosure include one or more application programming interfaces in an environment with user interface software interacting with a software application. Various function calls or messages are transferred via the application programming interfaces between the user interface software and software applications. Example application programming interfaces transfer function calls to implement scrolling, gesturing, and animating operations for a device.

At least certain embodiments of the present disclosure include an environment with user interface software interacting with a software application. A method for operating through an application programming interface (API) in this environment includes transferring a set bounce call. The method further includes setting at least one of maximum and minimum bounce values. The set bounce call causes a bounce of a scrolled region in an opposite direction of a scroll based on a region past an edge of the scrolled region being visible in a display region at the end of the scroll.

At least certain embodiments of the present disclosure include an environment with user interface software interacting with a software application. A method for operating through an application programming interface (API) in this environment includes transferring a rubberband call. Rubberbanding a scrolled region within a display region occurs by a predetermined maximum displacement when the scrolled region exceeds a display edge. The method further includes transferring an edge rubberband call to set displacement values for at least one edge of the display (e.g., top and bottom edges, left and right edges).

At least certain embodiments of the present disclosure include gesture operations for a display of a device. The gesture operations include performing a scaling transform such as a zoom in or zoom out in response to a user input having two or more input points. The gesture operations also include performing a rotation transform to rotate an image or view in response to a user input having two or more input points.

At least certain embodiments of the present disclosure include a method for performing animations for a display of a device. The method includes starting at least one animation. The method further includes determining the progress of each animation. The method further includes completing each animation based on a single timer. The single timer can be based on a redraw interval of the display hardware.

Various devices which perform one or more of the foregoing methods and machine readable media which, when executed by a processing system, cause the processing system to perform these methods, are also described.

Other methods, devices and machine readable media are also described.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure is described by way of example with reference to the accompanying drawings, wherein:

FIG. 1 is flow chart of a method for responding to a user input of a data processing device;

FIG. 2 illustrates details of an application programming interface in flow chart form according to certain teachings of the present disclosure;

FIG. 3 illustrates details of an application programming interface in flow chart form according to certain teachings of the present disclosure;

FIG. 4 is a schematic diagram illustrating an embodiment of user interface of a portable electronic device 400 having a touch-sensitive display 408;

FIG. 5A-5C illustrate at least some embodiments of user interface of a portable electronic device 400 having a touch-sensitive display;

FIG. 6A-6D illustrate the scrolling of a list of items to a terminus of the list, at which point an area beyond the terminus is displayed and the list is then scrolled in an opposite direction until the area beyond the terminus is no longer displayed, in accordance with some embodiments;

FIG. 7 illustrates details of an application programming interface in flow chart form according to certain teachings of the present disclosure;

FIG. 8 illustrates first and second scroll angles for locking a scroll of a display of a device in a horizontal or vertical direction according to certain teachings of the present disclosure;

FIG. 9 illustrates details of an application programming interface in flow chart form according to certain teachings of the present disclosure;

FIG. 10 illustrates details of an application programming interface in flow chart form according to certain teachings of the present disclosure;

FIG. 11 illustrates details of an application programming interface in flow chart form according to certain teachings of the present disclosure;

FIG. 12 illustrates details of an application programming interface in flow chart form according to certain teachings of the present disclosure;

FIG. 13 illustrates details of an application programming interface in flow chart form according to certain teachings of the present disclosure;

FIG. 14 illustrates details of an application programming interface in flow chart form according to certain teachings of the present disclosure;

FIG. 15 illustrates a display of a device having a scaling transform of a view;

FIGS. 16A and 16B illustrate a display of a device with a view having a first and a second scaling factor;

FIG. 16C illustrates changing a view from a scale factor of 2× to a scale factor of 1× in at least some embodiments of the present disclosure;

FIG. 17 illustrates details of an application programming interface in flow chart form according to certain teachings of the present disclosure;

FIG. 18 illustrates details of an application programming interface in flow chart form according to certain teachings of the present disclosure;

FIG. 19 is flow chart of a method for animating views displayed on a display of a device;

FIG. 20 is flow chart of a method for animating views displayed on a display of a device;

FIG. 21 illustrates details of an application programming interface in flow chart form according to certain teachings of the present disclosure;

FIGS. 22A and 22B illustrate synchronizing the resizing of windows of a display of a device;

FIG. 23 illustrates a method for switching ownership of a view of an application displayed on a display of a data processing device;

FIG. 24 illustrates a method for memory management of a view of an application displayed on a display of a device;

FIGS. 25A and 25B illustrate a data structure having a hierarchy of layers with a layer being associated with a view;

FIG. 26 illustrates a method for compositing media and non-media content of user interface for display on a device;

FIG. 27 illustrates a data structure or layer tree having a hierarchy of layers;

FIG. 28 is a perspective view of a device in accordance with one embodiment of the present disclosure;

FIG. 29 is a perspective view of a device in accordance with one embodiment of the present disclosure;

FIGS. 30A and 30B illustrate a device 3070 according to one embodiment of the disclosure;

FIG. 31 is a block diagram of a system in which embodiments of the present disclosure can be implemented;

FIG. 32 shows another example of a device in accordance with one embodiment of the present disclosure.

FIG. 33A is a perspective view of a device in a first configuration (e.g. in a laptop configuration) in accordance with one embodiment of the present disclosure;

FIG. 33B is a perspective view of the device of FIG. 33A in a second configuration (e.g. a transition configuration) in accordance with one embodiment of the present disclosure;

FIG. 33C is a perspective view of the device of FIG. 33A in a third configuration (e.g., a tablet configuration) in accordance with one embodiment of the present disclosure;

FIG. 34 illustrates details of an application programming interface in flow chart form according to certain teachings of the present disclosure; and

FIG. 35 illustrates a portion of a flow chart of a method for responding to a user input of a data processing device.

DETAILED DESCRIPTION OF THE INVENTION

Various embodiments and aspects of the disclosure will be described with reference to details discussed below, and the accompanying drawings will illustrate the various embodiments. The following description and drawings are illustrative of the disclosure and are not to be construed as limiting the disclosure. Numerous specific details are described to provide a thorough understanding of various embodiments of the present disclosure. However, in certain instances, well-known or conventional details are not described in order to provide a concise discussion of embodiments of the present disclosure.

Some portions of the detailed descriptions which follow are presented in terms of algorithms which include operations on data stored within a computer memory. An algorithm is generally a self-consistent sequence of operations leading to a desired result. The operations typically require or involve physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussion, it is appreciated that throughout the description, discussions utilizing terms such as “processing” or “computing” or “calculating” or “determining” or “displaying” or the like, can refer to the action and processes of a data processing system, or similar electronic device, that manipulates and transforms data represented as physical (electronic) quantities within the system's registers and memories into other data similarly represented as physical quantities within the system's memories or registers or other such information storage, transmission or display devices.

The present disclosure can relate to an apparatus for performing one or more of the operations described herein. This apparatus may be specially constructed for the required purposes, or it may comprise a general purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a machine (e.g. computer) readable storage medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, and magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), erasable programmable ROMs (EPROMs), electrically erasable programmable ROMs (EEPROMs), flash memory, magnetic or optical cards, or any type of media suitable for storing electronic instructions, and each coupled to a bus.

A machine-readable medium includes any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer). For example, a machine-readable medium includes read only memory (“ROM”); random access memory (“RAM”); magnetic disk storage media; optical storage media; flash memory devices; electrical, optical, acoustical or other form of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.); etc.

At least certain embodiments of the present disclosure include one or application programming interfaces in an environment with user interface software interacting with a software application. Various function calls or messages are transferred via the application programming interfaces between the user interface software and software applications. Transferring the function calls or messages may include issuing, initiating, invoking or receiving the function calls or messages. Example application programming interfaces transfer function calls to implement scrolling, gesturing, and animating operations for a device having a display region. An API may also implement functions having parameters, variables, or pointers. An API may receive parameters as disclosed or other combinations of parameters. In addition to the APIs disclosed, other APIs individually or in combination can perform similar functionality as the disclosed APIs.

The display region is a form of a window. A window is a display region which may not have a border and may be the entire display region or area of a display. In some embodiments, a display region may have at least one window and/or at least one view (e.g., web, text, or image content). A window may have at least one view. The methods, systems, and apparatuses disclosed can be implemented with display regions, windows, and/or views.

At least certain embodiments of the present disclosure include scrolling operations for scrolling a display of a device. The scrolling operations include bouncing a scrolled region in an opposite direction of a scroll when a scroll completes, rubberbanding a scrolled region by a predetermined maximum displacement when the scrolled region exceeds a display edge, and setting a scrolling angle that locks the scroll in a horizontal or vertical direction.

At least certain embodiments of the disclosure may be part of a digital media player, such as a portable music and/or video media player, which may include a media processing system to present the media, a storage device to store the media and may further include a radio frequency (RF) transceiver (e.g., an RF transceiver for a cellular telephone) coupled with an antenna system and the media processing system. In certain embodiments, media stored on a remote storage device may be transmitted to the media player through the RF transceiver. The media may be, for example, one or more of music or other audio, still pictures, or motion pictures.

The portable media player may include a media selection device, such as a click wheel input device on an iPod® or iPod Nano® media player from Apple Computer, Inc. of Cupertino, Calif., a touch screen input device, pushbutton device, movable pointing input device or other input device. The media selection device may be used to select the media stored on the storage device and/or the remote storage device. The portable media player may, in at least certain embodiments, include a display device which is coupled to the media processing system to display titles or other indicators of media being selected through the input device and being presented, either through a speaker or earphone(s), or on the display device, or on both display device and a speaker or earphone(s). In some embodiments, the display device and input device are integrated while in other embodiments the display device and input device are separate devices. Examples of a portable media player are described in published U.S. patent application numbers 2003/0095096 and 2004/0224638, both of which are incorporated by reference.

Embodiments of the disclosure described herein may be part of other types of data processing systems, such as, for example, entertainment systems or personal digital assistants (PDAs), or general purpose computer systems, or special purpose computer systems, or an embedded device within another device, or cellular telephones which do not include media players, or multi touch tablet devices, or other multi touch devices, or devices which combine aspects or functions of these devices (e.g., a media player, such as an iPod®, combined with a PDA, an entertainment system, and a cellular telephone in one device). In this disclosure, electronic devices and consumer devices are types of devices.

FIG. 1 is flow chart of a method for responding to a user input of a device. The method 100 includes receiving a user input at block 102. The user input may be in the form of an input key, button, wheel, touch, or other means for interacting with the device. The method 100 further includes creating an event object in response to the user input at block 104. The method 100 further includes determining whether the event object invokes a scroll or gesture operation at block 106. For example, a single touch that drags a distance across a display of the device may be interpreted as a scroll operation. In one embodiment, a two or more finger touch of the display may be interpreted as a gesture operation. In certain embodiments, determining whether the event object invokes a scroll or gesture operation is based on receiving a drag user input for a certain time period. The method 100 further includes issuing at least one scroll or gesture call based on invoking the scroll or gesture operation at block 108. The method 100 further includes responding to at least one scroll call, if issued, by scrolling a window having a view (e.g., web, text, or image content) associated with the event object based on an amount of a scroll with the scroll stopped at a predetermined position in relation to the user input at block 110. For example, an input may end at a certain position on a display of the device. The scrolling may continue until reaching a predetermined position in relation to the last input received from the user. The method 100 further includes responding to at least one gesture call, if issued, by changing a view associated with the event object based on receiving a plurality of input points in the form of the user input at block 112.

In certain embodiments of the present disclosure, scroll operations include attaching scroll indicators to a content edge of a display. Alternatively, the scroll indicators can be attached to the display edge. In some embodiments, user input in the form of a mouse/finger down causes the scroll indicators to be displayed on the display edge, content edge, or window edge of the scrolled region. If a mouse/finger up is then detected, the scroll indicators are faded out from the display region, content edge, or window edge of the scrolled region.

In certain embodiments of the present disclosure, gesture operations include responding to at least one gesture call, if issued, by rotating a view associated with the event object based on receiving a plurality of input points in the form of the user input. Gesture operations may also include scaling a view associated with the event object by zooming in or zooming out based on receiving the user input.

In some embodiments, a device includes a display region having multiple views or windows. Each window may have a multiple views including superviews and subviews. It is necessary to determine which window, view, superview, or subview is contacted by a user input in the form of a mouse up, mouse down, or drag, etc. An API can set various modes for making this determination. In one embodiment, a pass always mode sends mouse down, mouse up, and drag inputs to the nearest subview. In another embodiment, an intercept on drag mode sends a drag input to the superview while mouse up and down inputs are sent to the subview. In another embodiment, an intercept always mode sends all drag, mouse up and down inputs to the superview. The superview may be scroller software operating as a subclass of a view software. The subview may be view software operating as a subclass of the user interface software.

FIG. 2 illustrates details of an application programming interface in flow chart form according to certain teachings of the present disclosure. The application programming interface operates in an environment with user interface software interacting with a software application in order to provide a bounce operation. The method 200 for providing a bounce operation includes transferring a set bounce call at block 202. The method 200 further includes setting at least one of maximum and minimum bounce values at block 204. The minimum and maximum bounce values may be associated with at least one edge of a window that has received a user input. The method 200 further includes causing a bounce of a scrolled region in an opposite direction of a scroll based on a region past the scrolled region being visible in a display region at the end of the scroll at block 206. The scrolled region may be a content region.

In certain embodiments of the present disclosure, transferring the set bounce call is either one of issuing, initiating, invoking or receiving the set bounce call.

FIG. 3 illustrates details of an application programming interface in flow chart form according to certain teachings of the present disclosure. The application programming interface operates in an environment with user interface software interacting with a software application in order to provide a rubberband operation. The method 300 for providing a rubberband operation includes transferring a rubberband call to cause rubberbanding a scrolled region displayed within a display at block 302. The method 300 further includes transferring an edge rubberband call to set displacement values for at least one edge of the display at block 304. In some embodiments, the displacement values are set for top and bottom edges, left and right edges, or all edges.

Rubberbanding a scrolled region according to the method 300 occurs by a predetermined maximum displacement value when the scrolled region exceeds a display edge of a display of a device based on the scroll. If a user scrolls content of the display making a region past the edge of the content visible in the display, then the displacement value limits the maximum amount for the region outside the content. At the end of the scroll, the content slides back making the region outside of the content no longer visible on the display.

In certain embodiments of the present disclosure, transferring the rubberband call is either one of issuing, initiating, invoking or receiving the rubberband call.

FIG. 4 is a schematic diagram illustrating an embodiment of user interface of a portable electronic device 400 having a touch-sensitive display 408. The display 408 may include a window 410. The window 410 may include one or more displayed objects, such as information objects 412-1 to 412-4. In an exemplary embodiment, the information objects 412 may correspond to contact information for one or more individuals in a list of items. The displayed objects may be moved in response to detecting or determining movement 414 of a point of contact with the display, such as that associated with one or more digits 416 of a user (which are not drawn to scale in FIG. 4). In some embodiments, movement of the displayed objects may be accelerated in response to detecting or determining accelerated movement of the point of contact. While embodiment 400 includes one window 410, in other embodiments there may be two or more display windows. In addition, while embodiment 400 illustrates movement 414 in a particular direction, in other embodiments movement of the displayed objects may be in response to movement 414 in one or more other directions, or in response to a scalar (i.e., a determined or detected movement independent of the direction).

FIGS. 5A-5C illustrate the scrolling of a list of items on a device to a terminus of the list, at which point one or more displayed items at the end of the list smoothly bounce off the end of the display, reverse direction, and then optionally come to a stop. FIG. 5A is a schematic diagram illustrating an embodiment of user interface of a portable electronic device 400 having a touch-sensitive display. One or more displayed objects, such as information object 412-1 may be a distance 512-1 from a terminus 514 of the list of items which is an edge of a scrolled region and may be moving with a velocity 510-1 while the list is being scrolled. Note that the terminus 514 is a virtual boundary associated with the displayed objects, as opposed to a physical boundary associated with the window 410 and/or the display 408. As illustrated in FIG. 5B, when the one or more displayed objects, such as the information object 412-1, reach or intersect with the terminus 514, the movement corresponding to the scrolling may stop, i.e., the scrolling velocity may be zero at an instant in time. As illustrated in FIG. 5C, the one or more displayed objects, such as the information 412-1, may subsequently reverse direction. At a time after the intersection with the terminus 514, the information object 412-1 may have velocity 510-2 and may be a distance 512-2 from the terminus 514. In some embodiments, the magnitude of velocity 510-2 may be less than the magnitude of velocity 510-1 when the distance 512-2 equals the distance 512-1, i.e., the motion of the one or more displayed objects is damped after the scrolling list reaches and “bounces” at its terminus.

In at least some embodiments of the present disclosure, the method 200 performs the bounce operations described in FIGS. 5A-5C. The bounce call transferred at block 202 determines whether a bounce operation is enabled. The maximum and minimum bounces values determine the amount of bouncing of the scrolled region in an opposite direction of the scroll.

FIGS. 6A-6D illustrate the scrolling of a list of items to a terminus of the list, at which point an area beyond the terminus is displayed and the list is then scrolled in an opposite direction until the area beyond the terminus is no longer displayed, in accordance with some embodiments. The rubberband operation of method 300 is illustrated in the example of FIGS. 6A-6D with the listed items being email messages. FIGS. 6A-6D illustrate an exemplary user interface 3500A for managing an inbox in accordance with some embodiments. An analogous user interface may be used to display and manage other mailboxes (e.g., drafts, sent, trash, personal, etc.). In addition, other types of lists are possible, including but not limited to lists of instant message conversations, favorite phone numbers, contact information, labels, email folders, email addresses, physical addresses, ringtones, or album names.

If the list of emails fills more than the allotted screen area, the user may scroll through the emails using vertically upward and/or vertically downward swipe gestures on the touch screen. In the example of FIG. 6A, a portion of a list of emails is displayed in the screen area, including a top displayed email 3530 from Bruce Walker and a bottom displayed email 3532 from Kim Brook. A user performs a vertically downward swipe gesture 3514 to scroll toward the top of the list. The vertically downward gesture 3514 need not be exactly vertical; a substantially vertical gesture is sufficient. In some embodiments, a gesture within a predetermined angle of being perfectly vertical results in vertical scrolling.

As a result of detecting the vertically downward gesture 3514, in FIG. 6B the displayed emails have shifted down, such that the previous bottom displayed email 3532 from Kim Brook is no longer displayed, the previous top displayed email 3530 from Bruce Walker is now second from the top, and the email 3534 from Aaron Jones, which was not displayed in FIG. 6A, is now displayed at the top of the list.

In this example, the email 3534 from Aaron Jones is the first email in the list and thus is the terminus of the list. Upon reaching this email 3534, in response to continued detection of the vertically downward gesture 3514, an area 3536 (FIG. 6C) above the first email 3534 (i.e., beyond the terminus of the list) is displayed. In some embodiments, the area displayed beyond the terminus of the list is visually indistinct from the background of the list. In FIG. 6C, both the area 3536 and the background of the emails (e.g., emails 3534 and 3530) are white and thus are visually indistinct.

Once vertically downward gesture 3514 is complete, such that a corresponding object is no longer detected on or near the touch screen display, the list is scrolled in an opposite direction until the area 3536 is no longer displayed. FIG. 6D illustrates the result of this scrolling in the opposite direction, the email 3534 from Aaron Jones is now displayed at the top of the screen area allotted to the list and the area 3536 is not displayed.

In the example of FIGS. 6A-6D, a vertically downward gesture resulted in display of an area beyond the first item in the list. As described in FIG. 3, the values for the predetermined maximum displacement (e.g., display of an area beyond the first item in the list) are set at block 304 for top and bottom edges or at block 306 for all edges of the window.

Similarly, a vertically upward gesture may result in display of an area beyond the last item of the list, if the vertically upward gesture continues once the list has been scrolled to the last item. The last item may be considered a terminus of the list, similar to the first item. As discussed above, the gesture need not be exactly vertical to result in vertical scrolling; a gesture within a predefined range of angles from perfectly vertical is sufficient.

FIG. 7 illustrates details of an application programming interface in flow chart form according to certain teachings of the present disclosure. The application programming interface operates in an environment with user interface software interacting with a software application in order to provide a directional scrolling operation. The method 700 for operating through an application programming interface (API) includes transferring a directional scroll angle call to determine if directional scrolling is enabled at block 702. The method 700 further includes transferring a directional scroll angle call to set a scroll angle for locking the scrolling in at least one of a vertical or a horizontal direction at block 704. The method 700 further includes locking the scrolling in the horizontal direction if a user input forms an angle with a horizontal direction that is less than or equal to a first scroll angle at block 706. The method 700 further includes locking the scrolling in the vertical direction if a user input forms an angle with the vertical direction that is less than or equal to a second scroll angle at block 708.

In certain embodiments, a user input in the form of a drag forms an angle with the horizontal direction that is less than the first scroll angle. In this case, the user presumably intends to scroll in the horizontal direction. The scrolling will be locked in the horizontal direction until the user input exceeds the first scroll angle. A second scroll angle may be used for locking the user input in the vertical direction. The second scroll angle may be set equal to the first scroll angle.

FIG. 8 illustrates first and second scroll angles for locking a scroll of a display of a device in a horizontal or vertical direction. The horizontal direction 802 and vertical direction 804 are in reference to a window or a display of a device. As discussed in the method 700, a user input such as a drag movement forming an angle with the horizontal direction 802 less than or equal to the first scrolling angle 806 or 808 will lock the user input in the horizontal direction. In a similar manner, a user input forming an angle with the vertical direction 810 less than or equal to the second scrolling angle 810 or 812 will lock the user input in the vertical direction. The first and second scrolling angles may be set at the same angle or at different angles as well. For example, the first and second scrolling angles may be set at 25 degrees. A user input less than or equal to 25 degrees with respect to the horizontal or vertical direction will lock the scrolling in the appropriate direction.

In some embodiments, the horizontal and vertical locking angles can be determined in part by the aspect of the content. For example, content in the form of a tall page may receive a larger vertical locking angle compared to the horizontal locking angle.

FIG. 9 illustrates details of an application programming interface in flow chart form according to certain teachings of the present disclosure. The application programming interface operates in an environment with user interface software interacting with a software application in order to provide a deceleration scroll operation. The method 900 for providing the deceleration scroll operation includes transferring a deceleration scroll call to set a deceleration factor for a drag user input at block 902. The method 900 further includes slowing the scroll to a stop based on the speed of the drag user input and the deceleration factor at block 904.

In certain embodiments, a user input in the form of a drag invokes a scroll operation for a certain time period. The user input has a certain speed. The scroll of the scrolled region of a window or a display region of a display of a device will be stopped after the user input stops by applying a deceleration factor to the speed of the user input during the drag movement.

FIG. 10 illustrates details of an application programming interface in flow chart form according to certain teachings of the present disclosure. The application programming interface operates in an environment with user interface software interacting with a software application in order to provide a scroll hysteresis operation. The method 1000 for providing the scroll hysteresis operation includes transferring a scroll hysteresis call to determine whether a user input invokes a scroll at block 1002. The method 1000 further includes setting a hysteresis value for determining whether a user input invokes a scroll at block 1004.

In certain embodiments, a user input in the form of a drag over a certain distance across a display or window within a display of a device invokes a scroll operation. The hysteresis value determines the certain distance which the user input must drag across the display or window prior to invoking a scroll operation. A user input that does not drag the certain predetermined distance will not invoke a scroll operation and may be considered a mouse up or down input or other type of input.

FIG. 11 illustrates details of an application programming interface in flow chart form according to certain teachings of the present disclosure. The application programming interface operates in an environment with user interface software interacting with a software application in order to attach a scroll indicator to a scroll region edge or a window edge of a device. In some embodiments, the scroll region edge is associated with a content edge. The window or display edge may be associated with the edge of a display region. The method 1100 for providing the scroll indicator includes transferring a scroll indicator call to determine whether at least one scroll indicator attaches to an edge of a scroll region or a window edge at block 1102. A scroll indicator may be displayed on any display edge, window edge or scroll region edge. The method 1100 further includes optionally attaching at least one scroll indicator to the edge of the scroll region based on the scroll indicator call at block 1104. Alternatively, the method 1100 further includes optionally attaching at least one scroll indicator to the window edge of the view based on the scroll indicator call at block 1106.

In some embodiments, the operations of method 1100 can be altered, modified, combined, or deleted. For example, block 1104 can be deleted. Likewise, block 1106 can be deleted from the method 1100. Alternatively, the order of block 1104 and block 1106 can be switched. Other methods having various operations that have been disclosed within the present disclosure can also be altered, modified, rearranged, collapsed, combined, or deleted.

In certain embodiments of the present disclosure, transferring the scroll indicator call is either one of issuing, initiating, invoking or receiving the scroll indicator call. For example, the user interface software (e.g., software kit or library) may receive the scroll indicator call from the software application.

FIG. 12 illustrates details of an application programming interface in flow chart form according to certain teachings of the present disclosure. The application programming interface operates in an environment with user interface software interacting with a software application in order to determine if an inadvertent user input contacts a view of a display of a device. The method 1200 includes transferring an inadvertent user input call to determine whether the user input was inadvertent at block 1202. The method 1200 further includes ignoring the inadvertent user input based on the determination of the inadvertent user input call at block 1204. In one embodiment, the inadvertent user input call comprises a thumb detection call to determine whether the user input was an inadvertent thumb.

In certain embodiments of the present disclosure, transferring the inadvertent user input call is either one of issuing, initiating, invoking or receiving the inadvertent user input call.

A gesture API provides an interface between an application and user software in order to handle gesturing. Gesturing may include scaling, rotating, or other changes to a view, window, or display. A mask may merely permit certain changes while limiting or not permitting other changes. Events of all kinds come into the application via a graphics framework. They are enqueued, coalesced if necessary and dispatched. If the events are system level events (e.g., application should suspend, device orientation has changed, etc.) they are routed to the application having an instance of a class of the user interface software. If the events are hand events based on a user input, the events are routed to the window they occurred over. The window then routes these events to the appropriate control by calling the instance's mouse and gesture methods. The control that receives a mouse down or mouse entered function will continue to get all future calls until the hand is lifted. If a second finger is detected, the gesture methods or functions are invoked. These functions may include start, change, and end gesture calls. The control that receives start gesture call will be sent all future change gesture calls until the gesture ends.

FIG. 13 illustrates details of an application programming interface in flow chart form according to certain teachings of the present disclosure. The application programming interface operates in an environment with user interface software interacting with a software application in order to provide a gesture operation. The method 1300 for providing the gesture operation includes transferring a handle gesture event call at block 1302. The method 1300 further includes transferring a gesture change call in response to the handle gesture event call at block 1304.

In certain embodiments, a user input in the form of two or more points is received by a display of a device. A multi-touch driver of the device receives the user input and packages the event into an event object. A window server receives the event object and determines whether the event object is a gesture event object. If the window server determines that a gesture event object has been received, then user interface software issues or transfers the handle gesture call at block 1302 to a software application associated with the view. The software application confirms that a gesture event has been received and passes the handle gesture call to a library of the user interface software. The window server also associates the gesture event object with the view that received the user input. The library responds by transferring a gesture change call in response to the handle gesture event call at block 1304.

In one embodiment, a window or view associated with the user input receives the change call in order to perform the gesture event. The user software that provides the view receives a gesture start event call, a gesture changed event call, a zoom to scale setting for the view, and a gesture end call. The gesture calls receive an input of a gesture event which may be base event having a type such as a hand event, keyboard event, system event, etc. A delegate associated with the application receives a start gesture call, gesture did change call, and gesture did finish call. The user software is dynamically linking into the application during the run time of the gesture process.

In some embodiments, the gesture changed function call contains the following information about the gesture:

the number of fingers currently down;

the number of fingers initially down;

the rotation of the hand;

the scale of the hand;

the translation of the hand;

the position of the inner and outermost fingers; and

the pressure of the first finger.

In other embodiments, more information about each finger down may be included as follows:

the stage of the finger (just touch down, fully pressed, lifting off, etc.);

the position of the finger;

the proximity of the finger (how hard you're touching);

the orientation of the finger (what angle the ovoid is at);

the length of the major and minor axis;

the velocity of the finger; and

the eccentricity of the finger's ovoid.

A gesture event object may be a chord event object having a chord count (e.g., number of fingers contacted the view or display), a chord start event, a chord change event, and a chord end event. A chord change event may include a scaling or rotation transform.

FIG. 14 illustrates details of an application programming interface in flow chart form according to certain teachings of the present disclosure. The application programming interface operates in an environment with user interface software interacting with a software application in order to provide a scaling transform of a display region, window, or view of a display of a device. The method 1400 for providing the scaling transform includes transferring a scaling transform call to determine a scaling transform for a view associated with a user input having a plurality of input points at block 1402. The method 1400 further includes transferring a scaling gesture start call at block 1404. The method 1400 further includes transferring a scaling gesture progress call at block 1406. The method 1200 further includes transferring a scaling gesture end call at block 1408.

In certain embodiments, a user input in the form of two or more input points (e.g., fingers) moves together or apart to invoke a gesture event that performs a scaling transform on the view associated with the user input. A scale transform includes a minimum and maximum scale factor. FIG. 15 illustrates a display 1502 of a device having a scaling transform of a view. The view 1504 (e.g., web, text, or image content) has a first scale factor. A user input (e.g., two fingers moving apart) associated with the view 1504 is interpreted as a gesture event to zoom out from view 1504 to view 1508 having a second scale factor that exceeds the maximum scale factor of the view 1516. A snapback flag determines whether the zoom out can proceed past the maximum scale factor to view 1508 prior to snapping back to the maximum scale factor associated with view 1516.

FIG. 16A illustrates a display 1604 of a device having a first scaling factor of a view 1616. A user input (e.g., two fingers 1608 and 1610 moving together) associated with the view 1614 is interpreted as a gesture event to zoom in from view 1614 to view 1664 having a second scale factor as illustrated in FIG. 16B. The dashed regions 1602 and 1650 represent the total area of the content with the only content being displayed in the display area 1604 and 1652. In performing the scaling transform from FIG. 16A to FIG. 16B, the center of the gesture event, center 1612 for FIG. 16A and center 1660 for FIG. 16B, remains in the same position with respect to the display 1604. The scroll indicator 1606 shrinks to become scroll indicator 1654 during the transform to indicate that a smaller portion of the total content 1650 is being displayed on display 1604 as a result of the zoom in operation. The dashed region 1650 is larger than the dashed region 1602 to represent that a larger portion of content is not being displayed on display 1652 in FIG. 16B as a result of the zoom in operation.

In at least some embodiments of the present disclosure, a user desires to change a view 1670 from a scale factor of 2× to a scale factor of 1× as illustrated in FIG. 16C. A first set of user inputs 1672 and 1674 that move to the second set of user inputs 1676 and 1678 will decrease the scale factor from 2× to 1×. It may be desirable for the user to scale from 2× to 1× without having to move the user inputs a large distance across the view 1670. In an environment with user interface software interacting with a software application, a gesture scaling transform flag may be set in order to determine a scaling transform for a view associated with a user input having a plurality of input points. The scaling transform flag scales either from a current scale factor to a minimum scale factor or from the current scale factor to a maximum scale factor. For example, a flag may be set at the position associated with a 1.5× scale factor and a third set of user inputs 1680 and 1682. A user desiring to change the scale factor from 2× to 1× would only have to move his fingers, the user inputs, from the first set 1672 and 1674 to the third set 1680 and 1682 if the gesture scaling transform flag has been set at a scale factor of 1.5×.

FIG. 17 illustrates details of an application programming interface in flow chart form according to certain teachings of the present disclosure. The application programming interface operates in an environment with user interface software interacting with a software application in order to provide a rotation transform of a view, window, or display region of a display of a device. The method 1700 for providing the rotation transform includes transferring a rotation transform call to determine a rotation transform for a view associated with a user input having a plurality of input points at block 1702. The method 1700 further includes transferring a rotation gesture start call at block 1704. The method 1700 further includes transferring a scaling gesture progress call at block 1706. The method 1700 further includes transferring a scaling gesture end call at block 1708.

In certain embodiments, a user input in the form of two or more input points rotates to invoke a gesture event that performs a rotation transform on the view associated with the user input. The rotation transform includes a minimum and maximum degree of rotation for associated minimum and maximum rotation views. The user input may temporarily rotate a view past a maximum degree of rotation prior to the view snapping back to the maximum degree of rotation.

FIG. 18 illustrates details of an application programming interface in flow chart form according to certain teachings of the present disclosure. The application programming interface operates in an environment with user interface software interacting with a software application in order to notify a delegate of at least one animation associated with a display region, window, or view of a display of a device. A delay in the animation may be specified by the API. Also, multiple animations may be assigned priority by the API. The method 1800 for notifying the delegate includes determining whether any animation occurs at block 1802. The method 1800 further includes checking the progress of an animation at block 1804. If progress has occurred, then the next state (e.g., position, opacity, or transform) of the animation can be calculated at block 1806. If progress has completed at block 1806, then at block 1808 it is determined whether the view associated with the completed animation is associated with a delegate. If so, a delegate call is transferred to notify the delegate of the animation for the view at block 1810. The delegate operating under the control of the software application can change other views in response to the view being modified by the animation.

In certain embodiments, software invokes an animation that performs a scaling transform on the view associated with the user input. A display may include numerous views. The view being increased in size by the scaling transform may obstruct other views in which case the other views may need to be reduced in size. Alternatively, the view being decreased in size by the scaling transform may create additional area for other views to increase in size.

FIG. 19 is flow chart of a method for animating a display region, windows, or views displayed on a display of a device. The method 1900 includes starting at least two animations at block 1902. The method 1900 further includes determining the progress of each animation at block 1904. The method 1900 further includes completing each animation based on a single timer at block 1906.

In certain embodiments of the present disclosure, the single timer includes a timer based on a redraw interval which is a time period between the display of a current frame and a next frame of the display of the device. In this case, changes in animation are updated to the display during the redraw interval in order to display the changes during the next frame of the display. The progress of each animation may be calculated periodically or based upon a progress call.

The method 1900 may further include determining whether each animation is associated with a delegate. The delegate is then notified of the animation. Other views not associated with an animation may be changed depending on the software application controlling the delegate.

FIG. 20 is flow chart of a method for animating a display region, windows, or views displayed on a display of a device. The method 2000 includes providing a single animation timer at block 2002. The method 2000 further includes animating a plurality of animations with the single animation timer at block 2004. For example, a single timer may control all animations which occur simultaneously. The animations may include a transform, a frame, and an opacity animation. A animation transform may include a scaling or rotation transform. A frame animation may include resizing of a frame. An opacity animation changes the opacity from opaque to transparent or vice versa.

FIG. 21 illustrates details of an application programming interface in flow chart form according to certain teachings of the present disclosure. The application programming interface operates in an environment with user interface software interacting with multiple software applications or processes in order to synchronize animations associated with multiple views or windows of a display of a device. The method 2100 for synchronizing the animations includes setting attributes of views independently with each view being associated with a process at block 2102. For example, an attribute or property of a view may include a position, size, opacity, etc. An animation alters one or more attributes from a first state to a second state. The method 2100 further includes transferring a synchronization call to synchronize animations for the multiple views of the display at block 2104. The synchronization call may include input parameters or arguments such as an identification of the synchronization of the processes and a list of the processes that are requesting animation of the multiple views. In one embodiment, the synchronization call includes the identification and the number of processes that are requesting animation. In one embodiment, each application or process sends a synchronization call at different times. The method 2100 further includes transferring a synchronization confirmation message when a synchronization flag is enabled at block 2106. The synchronization flag can be enabled when the processes to be synchronized have each sent messages to a window server operating the user interface software. The method 2100 further includes updating the attributes of the views from a first state to a second state independently at block 2108. In one embodiment, the window server receives the updated attributes from each process at different times. The method 2100 further includes transferring a start animation call to draw the requested animations when both processes have updated attributes associated with the second state at block 2110.

In some embodiments, a first data structure or layer tree represents a hierarchy of layers that correspond to the views or windows of the processes. A second data structure or render tree represents a similar copy of the layer tree. However, the render tree is not updated until the independent processes have completed their separate animations. At this time, the render tree updates and redraws the screen with the new animations.

FIGS. 22A and 22B illustrate synchronizing the resizing of views or windows of a display of a device. For example, a window 2210 associated with a first process with a size attribute may increase in size by changing from a first state, window 2210 in FIG. 22A, to a second state, window 2210 in FIG. 22B. At approximately the same time, a second window 2220 may decrease in size in proportion to the increase in size of the first window 2210. The method 2100 provides synchronization of the resizing of the windows 2210 and 2220 illustrated in FIGS. 22A and 22B. The animations in changing from the first state to the second state may occur incrementally and occur with the synchronization of method 2100.

FIG. 23 illustrates a method for switching ownership of a view of an application displayed on a display of a data processing device. The method 2300 includes constructing a data structure having a hierarchy of layers with a layer being associated with a view and owning the view at block 2302. The layers may be content, windows, video, images, text, media, or any other type of object for user interface of the application. The method 2300 further includes removing the layer from the data structure at block 2304. The method 2300 further includes switching ownership of the view from the layer to the view at block 2306.

In some embodiments, each layer from the data structure is associated with a view. The layer associated with the view sends a delegate function call to the view in order to generate content provided by the view. A first pointer reference points from the layer to the view. A second pointer reference points from the view to the layer. The number of references pointing to an object such as the view is defined as the retained count of the object. The view may receive notification that the layer will be removed from the data structure. Removing the layer from the data structure may occur based on the view associated with the layer being removed from the display of the device. When the layer is removed from the data structure or layer tree the pointer from the layer to the view will be removed. The view will have a retained count of zero and be deallocated or removed from memory if the ownership of the view is not reversed. The view will have a retained count of at least one if ownership is reversed.

FIG. 24 illustrates a method for memory management of a view of an application displayed on a display of a device. The method 2400 includes constructing a data structure having a hierarchy of layers with at least one layer being associated with the view at block 2402. The method 2400 further includes storing the data structure in memory at block 2404. The method 2400 further includes maintaining a retained count of the number of references to the view from other objects at block 2406. The method 2400 further includes deallocating the view from memory if the retained count is zero at block 2408. As discussed above, the retained count of the view will be decremented if the layer is removed from the data structure. Removing the layer from the data structure may occur based on the view associated with the layer being removed from the display of the device.

FIGS. 25A and 25B illustrate a data structure having a hierarchy of layers with a layer being associated with a view. The data structure includes layers 2502, 2504, and 2506. Layer 2506 is associated with the view 2510. The layer 2506 associated with the 2510 view sends a delegate call to the view in order to generate content provided by the view. A first pointer reference 2508 points from the layer 2506 to the view 2510. A second pointer reference 2512 points from the view 2510 to the layer 2506. A third pointer reference 2532 may point from user interface (UI) controller 2530 to the view 2510. The UI controller 2530 may control operations associated with the view 2510 such as scrolling the view 2510 in response to a user input. The view 2510 in FIG. 25A has a retained count of two based on the pointer references 2508 and 2532.

If the layer 2506 is removed from the data structure as illustrated in FIG. 25B, then the pointer 2508 is removed. View 2510 will have a lower retained count as illustrated in FIG. 25B. If view 2510 has a retained count of zero, then the memory storing the view 2510 will be deallocated.

FIG. 26 illustrates a method for compositing media and non-media content of user interface for display on a device. The method 2600 includes constructing a data structure having a hierarchy of layers associated with the user interface of the device at block 2602. The method 2600 further includes determining whether each layer of the data structure is associated with media or non-media content at block 2604. The data structure or layer tree is traversed in order to determine whether each of the layers of the data structure is associated with media or non-media content. The method 2600 further includes detaching a layer associated with media content from the data structure at block 2606. The method 2600 further includes storing media content in a first memory location at block 2606. The method 2600 further includes storing non-media content in a second memory location at block 2608. The method 2600 further includes compositing the media and non-media content for display on the device at block 2610.

In some embodiments, compositing the media and non-media content includes retrieving the media content from the first memory location, retrieving the non-media content from the second memory location, and scanning the media and non-media content directly to the display. The memory location can be any type of memory located in cache, main memory, a graphics processing unit, or other location within a device. The media content may include video, video plug-in, audio, image, or other time varying media. The media content may be in the form of a YUV model with the Y representing a luminance component (the brightness) and U and V representing chrominance (color) components. The media content may be scanned to the display at a rate of substantially twenty to forty frames per second. The media content may be scaled prior to being scanned to the display of the device.

The non-media content may include content, views, and images that do not require frequent updating. The non-media content may be in the form of a RGB model which is an additive model in which red, green, and blue (often used in additive light models) are combined in various ways to reproduce other colors. The non-media content may be scanned to the display at a slower rate compared to the media content.

FIG. 27 illustrates a data structure or layer tree having a hierarchy of layers. The layers can be associated with media and non-media content. For example, layer 2704 is associated with media content 2706 such as a video. Layer 2710 is associated with non-media content 2712 which may be user interface view for the video. Layers 2720, 2730, and 2740 are associated with non-media content 2722, 2732, and 2742, respectively, that forms the components of the non-media content 2712. The method 2600 will determine whether each layer of the data structure is associated with media or non-content. Any layers associated with media content such as layer 2704 will be removed from the data structure and processed in a separate memory location.

In some embodiments, the methods, systems, and apparatuses of the present disclosure can be implemented in various devices including electronic devices, consumer devices, data processing devices, desktop computers, portable computers, wireless devices, cellular devices, tablet devices, handheld devices, multi touch devices, multi touch data processing devices, any combination of these devices, or other like devices. FIGS. 4-6 and 28-33 illustrate examples of a few of these devices.

FIG. 28 illustrates a device 2800 according to one embodiment of the disclosure. FIG. 28 shows a wireless device in a telephone configuration having a “candy-bar” style. In FIG. 28, the wireless device 2800 may include a housing 2832, a display device 2834, an input device 2836 which may be an alphanumeric keypad, a speaker 2838, a microphone 2840 and an antenna 2842. The wireless device 2800 also may include a proximity sensor 2844 and an accelerometer 2846. It will be appreciated that the embodiment of FIG. 28 may use more or fewer sensors and may have a different form factor from the form factor shown in FIG. 28.

The display device 2834 is shown positioned at an upper portion of the housing 2832, and the input device 2836 is shown positioned at a lower portion of the housing 2832. The antenna 2842 is shown extending from the housing 2832 at an upper portion of the housing 2832. The speaker 2838 is also shown at an upper portion of the housing 2832 above the display device 2834. The microphone 2840 is shown at a lower portion of the housing 2832, below the input device 3286. It will be appreciated that the speaker 2838 and microphone 2840 can be positioned at any location on the housing, but are typically positioned in accordance with a user's ear and mouth, respectively.

The display device 2834 may be, for example, a liquid crystal display (LCD) which does not include the ability to accept inputs or a touch input screen which also includes an LCD. The input device 2836 may include, for example, buttons, switches, dials, sliders, keys or keypad, navigation pad, touch pad, touch screen, and the like. Any well-known speaker, microphone and antenna can be used for speaker 2838, microphone 2840 and antenna 2842, respectively.

The data acquired from the proximity sensor 2844 and the accelerometer 2846 can be combined together, or used alone, to gather information about the user's activities. The data from the proximity sensor 2844, the accelerometer 2846 or both can be used, for example, to activate/deactivate a display backlight, initiate commands, make selections, control scrolling, gesturing, animating or other movement in a display, control input device settings, or to make other changes to one or more settings of the device. In certain embodiments of the present disclosure, the device 2800 can be used to implement at least some of the methods discussed in the present disclosure.

FIG. 29 shows a device 2950 in accordance with one embodiment of the disclosure. The device 2950 may include a housing 2952, a display/input device 2954, a speaker 2956, a microphone 2958 and an optional antenna 2960 (which may be visible on the exterior of the housing or may be concealed within the housing). The device 2950 also may include a proximity sensor 2962 and an accelerometer 2964. The device 2950 may be a cellular telephone or a device which is an integrated PDA and a cellular telephone or a device which is an integrated media player and a cellular telephone or a device which is both an entertainment system (e.g. for playing games) and a cellular telephone, or the device 2950 may be other types of devices described herein. In one particular embodiment, the device 2950 may include a cellular telephone and a media player and a PDA, all contained within the housing 2952. The device 2950 may have a form factor which is small enough that it fits within the hand of a normal adult and is light enough that it can be carried in one hand by an adult. It will be appreciated that the term “portable” means the device can be easily held in an adult user's hands (one or both); for example, a laptop computer and an iPod are portable devices.

In one embodiment, the display/input device 2954 may include a multi-point touch input screen in addition to being a display, such as an LCD. In one embodiment, the multi-point touch screen is a capacitive sensing medium configured to detect multiple touches (e.g., blobs on the display from a user's face or multiple fingers concurrently touching or nearly touching the display) or near touches (e.g., blobs on the display) that occur at the same time and at distinct locations in the plane of the touch panel and to produce distinct signals representative of the location of the touches on the plane of the touch panel for each of the multiple touches.

In certain embodiments of the present disclosure, the device 2800 can be used to implement at least some of the methods discussed in the present disclosure.

FIGS. 30A and 30B illustrate a device 3070 according to one embodiment of the disclosure. The device 3070 may be a cellular telephone which includes a hinge 3087 that couples a display housing 3089 to a keypad housing 3091. The hinge 3087 allows a user to open and close the cellular telephone so that it can be placed in at least one of two different configurations shown in FIGS. 30A and 30B. In one particular embodiment, the hinge 3087 may rotatably couple the display housing to the keypad housing. In particular, a user can open the cellular telephone to place it in the open configuration shown in FIG. 30A and can close the cellular telephone to place it in the closed configuration shown in FIG. 30B. The keypad housing 3091 may include a keypad 309S which receives inputs (e.g. telephone number inputs or other alphanumeric inputs) from a user and a microphone 3097 which receives voice input from the user. The display housing 3089 may include, on its interior surface, a display 3093 (e.g. an LCD) and a speaker 3098 and a proximity sensor 3084; on its exterior surface, the display housing 3089 may include a speaker 3096, a temperature sensor 3094, a display 3088 (e.g. another LCD), an ambient light sensor 3092, and a proximity sensor 3084A. Hence, in this embodiment, the display housing 3089 may include a first proximity sensor on its interior surface and a second proximity sensor on its exterior surface.

In at least certain embodiments, the device 3070 may contain components which provide one or more of the functions of a wireless communication device such as a cellular telephone, a media player, an entertainment system, a PDA, or other types of devices described herein. In one implementation of an embodiment, the device 3070 may be a cellular telephone integrated with a media player which plays MP3 files, such as MP3 music files.

Each of the devices shown in FIGS. 4, 5A, 5B, 5C, 6A, 6B, 6C, 6D, 28, 29, 30A and 30B may be a wireless communication device, such as a cellular telephone, and may include a plurality of components which provide a capability for wireless communication. FIG. 31 shows an embodiment of a wireless device 3070 which includes the capability for wireless communication. The wireless device 3070 may be included in any one of the devices shown in FIGS. 4, 5A, 5B, 5C, 6A, 6B, 6C, 6D, 28, 29, 30A and 30B, although alternative embodiments of those devices of FIGS. 4, 5A, 5B, 5C, 6A, 6B, 6C, 6D, 28, 29, 30A and 30B may include more or fewer components than the Wireless device 3070.

Wireless device 3070 may include an antenna system 3101. Wireless device 3070 may also include a digital and/or analog radio frequency (RF) transceiver 3102, coupled to the antenna system 3101, to transmit and/or receive voice, digital data and/or media signals through antenna system 3101.

Wireless device 3070 may also include a digital processing system 3103 to control the digital RF transceiver and to manage the voice, digital data and/or media signals. Digital processing system 3103 may be a general purpose processing device, such as a microprocessor or controller for example. Digital processing system 3103 may also be a special purpose processing device, such as an ASIC (application specific integrated circuit), FPGA (field-programmable gate array) or DSP (digital signal processor). Digital processing system 3103 may also include other devices, as are known in the art, to interface with other components of wireless device 3070. For example, digital processing system 3103 may include analog-to-digital and digital-to-analog converters to interface with other components of wireless device 3070. Digital processing system 3103 may include a media processing system 3109, which may also include a general purpose or special purpose processing device to manage media, such as files of audio data.

Wireless device 3070 may also include a storage device 3104, coupled to the digital processing system, to store data and/or operating programs for the Wireless device 3070. Storage device 3104 may be, for example, any type of solid-state or magnetic memory device.

Wireless device 3070 may also include one or more input devices 3105, coupled to the digital processing system 3103, to accept user inputs (e.g., telephone numbers, names, addresses, media selections, etc.) Input device 3105 may be, for example, one or more of a keypad, a touchpad, a touch screen, a pointing device in combination with a display device or similar input device.

Wireless device 3070 may also include at least one display device 33106, coupled to the digital processing system 3103, to display information such as messages, telephone call information, contact information, pictures, movies and/or titles or other indicators of media being selected via the input device 3105. Display device 3106 may be, for example, an LCD display device. In one embodiment, display device 3106 and input device 3105 may be integrated together in the same device (e.g., a touch screen LCD such as a multi-touch input panel which is integrated with a display device, such as an LCD display device). The display device 3106 may include a backlight 3106A to illuminate the display device 3106 under certain circumstances. It will be appreciated that the Wireless device 3070 may include multiple displays.

Wireless device 3070 may also include a battery 3107 to supply operating power to components of the system including digital RF transceiver 3102, digital processing system 3103, storage device 3104, input device 3105, microphone 3105A, audio transducer 3108, media processing system 3109, sensor(s) 3110, and display device 3106. Battery 3107 may be, for example, a rechargeable or non-rechargeable lithium or nickel metal hydride battery. Wireless device 3070 may also include audio transducers 3108, which may include one or more speakers, and at least one microphone 3105A. In certain embodiments of the present disclosure, the wireless device 3070 can be used to implement at least some of the methods discussed in the present disclosure.

FIG. 32 shows another example of a device according to an embodiment of the disclosure. This device 3200 may include a processor, such as microprocessor 3202, and a memory 3204, which are coupled to each other through a bus 3206. The device 3200 may optionally include a cache 3208 which is coupled to the microprocessor 3202. This device may also optionally include a display controller and display device 3210 which is coupled to the other components through the bus 3206. One or more input/output controllers 3212 are also coupled to the bus 3206 to provide an interface for input/output devices 3214 and to provide an interface for one or more sensors 3216 which are for sensing user activity. The bus 3206 may include one or more buses connected to each other through various bridges, controllers, and/or adapters as is well known in the art. The input/output devices 3214 may include a keypad or keyboard or a cursor control device such as a touch input panel. Furthermore, the input/output devices 3214 may include a network interface which is either for a wired network or a wireless network (e.g. an RF transceiver). The sensors 3216 may be any one of the sensors described herein including, for example, a proximity sensor or an ambient light sensor. In at least certain implementations of the device 3200, the microprocessor 3202 may receive data from one or more sensors 3216 and may perform the analysis of that data in the manner described herein. For example, the data may be analyzed through an artificial intelligence process or in the other ways described herein. As a result of that analysis, the microprocessor 3202 may then automatically cause an adjustment in one or more settings of the device.

In certain embodiments of the present disclosure, the device 3200 can be used to implement at least some of the methods discussed in the present disclosure.

FIGS. 33A-C show another example of a device according to at least certain embodiments of the disclosure. FIG. 33A illustrates a laptop device 3300 with a keyboard 3302, a body 3304, a display frame 3306, and a display 3308. The laptop device 3300 can be converted into a tablet device as illustrated in FIG. 33B and FIG. 33C. FIG. 33B illustrates the conversion of the laptop device into a tablet device. An edge of a display frame 3356 containing a display 3358 is slide within the body 3354 across the top of a keyboard 3352 until forming a tablet device as illustrated in FIG. 33C. The tablet device with a display 2362 and a display frame 3366 rests on top of a body 3360.

In certain embodiments of the present disclosure, the laptop device 3300 can be used to implement at least some of the methods discussed in the present disclosure.

FIG. 34 illustrates details of an application programming interface in flow chart form according to certain teachings of the present disclosure. The application programming interface operates in an environment with user interface software interacting with a software application. In some embodiments, a hierarchy of views operates on top of a hierarchy of layers within the user interface software. The API operates as illustrated in method 3400 that includes constructing a hierarchy of views operating on top of a hierarchy of layers at block 3402. The method 3400 further includes providing access to the hierarchy of views without providing access to the hierarchy of layers at block 3404. An application may interact with the hierarchy of views via the API without accessing the hierarchy of layers operating below the hierarchy of views.

In some embodiments, a platform provides various scrolling, gesturing, and animating operations. The platform includes hardware components and an operating system. The hardware components may include a processing unit coupled to an input panel and a memory coupled to the processor. The operating system includes one or more programs that are stored in the memory and configured to be executed by the processing unit. One or more programs include various instructions for transferring function calls or messages through an application programming interface in order to perform various scrolling, gesturing, and animating operations.

In an embodiment, the one or more programs include instructions for transferring a bounce call through an API to cause a bounce of a scrolled region in an opposite direction of a scroll based on a region past an edge of the scrolled region being visible in a display region at the end of the scroll. In an embodiment, the one or more programs include instructions for transferring a rubberband call through an API to cause a rubberband effect on a scrolled region by a predetermined maximum displacement when the scrolled region exceeds a display edge based on a scroll. In an embodiment, the one or more programs include instructions for transferring a directional scroll call through an API to set a scroll angle for locking the scrolling in at least one of a vertical or a horizontal direction.

In an embodiment, the one or more programs include instructions for transferring a scroll hysteresis call through an API to determine whether a user input invokes a scroll. In an embodiment, the one or more programs include instructions for transferring a deceleration scroll call through an API to set a deceleration factor for a user input based on the user input invoking a scroll. In an embodiment, the one or more programs include instructions for transferring a scroll indicator call through an API to determine whether at least one scroll indicator attaches to a content edge or a display edge of a display region.

In some embodiments, the platform includes a framework containing a library of software code. The framework interacts with the programs of the platform to provide application programming interfaces for performing various scrolling, gesturing, and animating operations. The framework also includes associated resources (e.g., images, text, etc.) that are stored in a single directory.

In an embodiment, the library of the framework provides an API for specifying a bounce operation to cause a bounce of a scrolled region in an opposite direction of a scroll based on a region past an edge of the scrolled region being visible in a display region at the end of the scroll. In an embodiment, the library of the framework provides an API for specifying a rubberband operation that has a rubberband effect on a scrolled region by a predetermined maximum displacement when the scrolled region exceeds a display edge based on a scroll. In an embodiment, the library of the framework provides an API for specifying a directional scroll operation to set a scroll angle for locking the scrolling in at least one of a vertical or a horizontal direction.

In an embodiment, the library of the framework provides an API for specifying a scroll hysteresis operation to determine whether a user input invokes a scroll. In an embodiment, the library of the framework provides an API for specifying a deceleration scroll operation to set a deceleration factor for a user input based on the user input invoking a scroll. In an embodiment, the library of the framework provides an API for specifying a scroll indicator operation to determine whether at least one scroll indicator attaches to a content edge or a display edge of a display region.

In the foregoing specification, the disclosure has been described with reference to specific exemplary embodiments thereof. It will be evident that various modifications may be made thereto without departing from the broader spirit and scope of the disclosure as set forth in the following claims. The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense.

APPENDIX A

API SOFTWARE CODE

1
− (AffineTransform)transform;

2
− (void)setTransform:(AffineTransform)transform: // animatable

3

4
@interface UIView(Animation)

5

6
+ (void)beginAnimation: (String*)animationIDS; // animationID can be nil

if you don't

7
want to have an identifier for the group

8
+ (void)beginAnimations: (String*)animationID context: (void*) context //

additional context info

9
passed to will start/did stop selectors

10
+(void)endAnimations;

11

12
+(void)setAnimationDelegate:(id)delegate;

13
+(void)setAnimationDuration: (TimeInterval)duration;

14
+(void)setAnimationDelay:(TimeInterval)delay;

15
+(void)setAnimationStartTime:(AbsoluteTime)start;

16
+(void)setAnimationCurve:(UIViewAnimationCurve)curve;

17

18
(BOOL)handleEvent:(Event)event;

19

20
// this is called if the app is going to be suspending back to a previous

21
application.

22
// the app should return YES if it is going to perform animation, otherwise it

should

23
// return NO. The startTime argument is a start time for any animations to begin

so that

24
// the animations are synchronized with a window server. If the application's

25
// implementation of this method returns YES, it should later call [UIApp

26
suspendWith ANimation:NO] when

27
// it is finished animating.

28
(BOOL)animateSuspensionRetumingToLastApp:AbsoluteTime)startTime;

29

30
// Set the status bar mode, orientation over duration. If processSynchID is non-

zero, used as

31
sync ID.

32
− (void) setStatusBarMode: (UIStatusBarMode) mode

33
orientation: (UIStatusBarOrientation) orientation duration:(float)duration

34
processSynchID: (int)processSynchID;

35
// Sets the status bar mode. 0 duration means no animation

36
− (void) setStatusBarMode: (UIStatusBarMode)mode

37
orientation: (UIStatusBarOrientation)orientation duration: (float)duration;

38
− (void) setStatusBarMode: (UIStatusBarMode)mode duration:(float)duration; //

39
uses the default orientation.

40
− (UIStatusBarOrientation) statusBarOrientation;

41
− (UIStatusBarOrientation) statusBarMode;

42
// Status bar rect in non-rotated window coordinates.

43

44
− (void) synchronizedDrawingWithID: (int)processSynchID; // used for status

bar

45
resize

46
//______________________________________________________________

47

48
// Gesture delegate method. event will be nil if gesture was not event-driven (ie

49
programatically or animation).

50
@interface Object(UIViewGestureDelegate)

51

52
− (void)willStartGestures: (UIView *)view forEvent: (GSEvent)event;

53

54
− (void)didFinishGestures: (UIView *)view forEvent:(Event)event;

55

56
− (void)willStartGesture: (UIGestureType)type inView: (UIView *) view

57
forEvent: (Event)event;

58

59
− (void)gestureDidChange: (UIGestureType)type inView: (UIView *) view

60
forEvent: (Event)event;

61

62
− (void)didFinishGesture: (UIGestureType)type inView: (UIView *) view

63
forEvent: (Event)event;

64
@end

65

66
UIGestureAttributeZooms // Number (BOOL)

67

68
typedef enum {

69
UIScrollerEventModelnterceptOnDrag, // send mouseDown /

mouseUp to subviews if

70
not dragged

71
UIScrollerEventModePass, // send

72
mouseDown/mouseDrag/mouseUp to subviews

73
UIScrollerEventModeIntercept, // send mouseDown / mouseUp to

subviews

74
} UIScrollerEventMode;

75
− (void)setEventMode:(UIScrollerEventMode)mode;

76

77
− (void)setDirectionalScrolling:(BOOL )flag;

78

79
− (void)setDirectionalScrollingAngle :(float)flag;

80

81
− (void)setScrollDecelerationFactor:(float)factor;

82

83
− (void)setBounces:(BOOL)bounces;

84

85
− (void)setThumbDetectionEnabled:(BOOL )flag;

86

87
− (void)setShowScrollerIndicators:(BOOL)flag;

88

89
− (void)setScrollerIndicator:(Rect)rect;

90

91
− (void)setScrollerIndicatorsPinToContent:(BOOL)flag;

92

93

94
− (void)setAllowsRubberBanding:(BOOL)flag; // CallsetRubberBand: forEdges:

with

95
RUBBER_BAND_HEIGHT for the top and bottom edges

96

97
− (void)setAllowsFourWayRubberBanding:(BOOL)flag; // Calls

98
setRubberBand: for Edges: with RUBBER_BAND_HEIGHT for all edges

99

100
− (void)setRubberBand: (float) value for Edges:(UIRectEdge) edges: //

Default

101
set for top and bottom edges

102

103
− (void)contentMouseUpin View:(UIView*)mouseUp View

104
withEvent:(Event)event; // default calls -mouseUp; on view

105

106
− (Point)scroller:(UIScroller *)scroller

107
adjustSmoothScrollEnd:(Point)offset velocity:(Size )velocity;

108

109
@interfacebject (UIAnimationDelegate)

110
− (void)animator: (UIAnimator*)animator

111
startAnimation:(UIAnimation*)animation;

112
− (void)animator: (UIAnimator*)animator

113
stopAnimation:(UIAnimation*)animation;

114
− (void)animator: (UIAnimator*)animator stopAnimation:

(UIAnimation*)animation

115
fraction: (float) fraction;

116
@end

117
//_______________________________________________________________________

118
@interface UITransformAnimation : UIAnimation {

119
@protected

120
AffineTransform _startTransform

121
AffineTransform _endTransform

122
}

123
(void)set StartTransform: (AffineTransform)start;

124
−(void)setEndTransform: (AffineTransform)end;

125
−(AffineTransform)transformForFraction: (float) fraction;

126
@end

127
//_______________________________________________________________________

128
@interface UIFrameAnimation : UIAnimation {

129
Rect _startFrame;

130
Rect _endFrame;

131
UIRectFields _fieldsToChange;

132
}

133
− (void) setStartFrame: (Rect)start;

134
− (void) setEndFrame: (Rect)end;

135
− (void) setSignificantRectFields: (UIRectFields)fields;

136

137
−(Rect)endFrame;

138

139
@end

140

141
@interface UIAlphaAnimation : UIAnimation {

142
@protected

143
float _startAlpha;

144
float _endAlpha;

145
}

146
− (void)setStartAlpha: (float)start;

147
− (void)setEndAlpha: (float)end;

148
− (void)alphaForFraction: (float)fraction;

149

150
@end

151

152
@interface UIRotationAnimation : UIAnimation {

153
float _startAngle;

154
float _endAngle;

155
− (void)setStartRotationAngle: (float)degrees;

156
− (void)setEndRotationAngle: (float) degrees;

Claims

1. A non-transitory computer-readable storage medium storing executable program instructions, which when executed by an electronic device with a processor and a touch-sensitive display, cause the device to: receive a user input, the user input is one or more input points applied to the touch-sensitive display;create an event object in response to the user input;determine whether the event object invokes a scroll or gesture operation by distinguishing between the user input consisting of a single input point that moves a distance across the touch-sensitive display that is interpreted as the scroll operation, and the user input consisting of a plurality of input points applied to the touch-sensitive display that are interpreted as the gesture operation; andissue at least one scroll or gesture call based on invoking the scroll or gesture operation, wherein the gesture operation is at least one of a scaling operation and a rotating operation.
2. The medium of claim 1, the executable program instructions, when executed by the device, further cause the device to: while the scroll operation is invoked: in accordance with a determination that an angle formed by the user input with a horizontal line on the touch-sensitive display is less than a threshold angle, lock the scrolling in a horizontal direction; andin accordance with a determination that an angle formed by the user input with a vertical line on the touch-sensitive display is less than the threshold angle, lock the scrolling in a vertical direction.
3. The medium of claim 1, the executable program instructions, when executed by the device, further cause the device to: while the scroll operation is invoked: scroll a window associated with the event object;rubberband a scrolled region of the window by a predetermined maximum displacement value as the scrolled region exceeds an edge of the window; andbounce the scrolled region in an opposite direction of the scroll in response to termination of the user input.
4. The medium of claim 1, wherein the executable program instructions, when executed by the device, further cause the device to: while the scaling operation is invoked: scale a view associated with the event object while maintaining a center of the view as a center of the scaled view.
5. The medium of claim 1, wherein the executable program instructions, when executed by the device, further cause the device to: while the scaling operation is invoked: scale a view associated with the event object based on a scale factor that is within a range of a minimum scale factor and a maximum scale factor, the minimum and maximum scale factors being associated with the event object, wherein the scale factor is determined based on movement of the plurality of input points of the user input on the touch-sensitive display.
6. The medium of claim 1, wherein the executable program instructions, when executed by the device, further cause the device to: while the rotating operation is invoked: rotate a view associated with the event object by a rotation angle that is within a range of a minimum rotation angle and a maximum rotation angle, the minimum and maximum rotation angles being associated with the event object, wherein the rotation angle is determined based on movement of the plurality of input points of the user input on the touch-sensitive display.
7. An electronic device, comprising: a touch-sensitive display;one or more processors;a memory storing executable program instructions, which when executed by the one or more processors, cause the device to: receive a user input, the user input is one or more input points applied to the touch-sensitive display;create an event object in response to the user input;determine whether the event object invokes a scroll or gesture operation by distinguishing between the user input consisting of a single input point that moves a distance across the touch-sensitive display that is interpreted as the scroll operation, and the user input consisting of a plurality of input points applied to the touch-sensitive display that are interpreted as the gesture operation; andissue at least one scroll or gesture call based on invoking the scroll or gesture operation, wherein the gesture operation is at least one of a scaling operation and a rotating operation.
8. The device of claim 7, the executable program instructions, when executed by the one or more processors, further cause the device to: while the scroll operation is invoked: in accordance with a determination that an angle formed by the user input with a horizontal line on the touch-sensitive display is less than a threshold angle, lock the scrolling in a horizontal direction; andin accordance with a determination that an angle formed by the user input with a vertical line on the touch-sensitive display is less than the threshold angle, lock the scrolling in a vertical direction.
9. The device of claim 7, the executable program instructions, when executed by the one or more processors, further cause the device to: while the scroll operation is invoked: scroll a window associated with the event object;rubberband a scrolled region of the window by a predetermined maximum displacement value as the scrolled region exceeds an edge of the window; andbounce the scrolled region in an opposite direction of the scroll in response to termination of the user input.
10. The device of claim 7, the executable program instructions, when executed by the one or more processors, further cause the device to: while the scaling operation is invoked: scale a view associated with the event object while maintaining a center of the view as a center of the scaled view.
11. The device of claim 7, the executable program instructions, when executed by the one or more processors, further cause the device to: while the scaling operation is invoked: scale a view associated with the event object based on a scale factor that is within a range of a minimum scale factor and a maximum scale factor, the minimum and maximum scale factors being associated with the event object, wherein the scale factor is determined based on movement of the plurality of input points of the user input on the touch-sensitive display.
12. The device of claim 7, the executable program instructions, when executed by the one or more processors, further cause the device to: while the rotating operation is invoked: rotate a view associated with the event object by a rotation angle that is within a range of a minimum rotation angle and a maximum rotation angle, the minimum and maximum rotation angles being associated with the event object, wherein the rotation angle is determined based on movement of the plurality of input points of the user input on the touch-sensitive display.
13. A method, comprising: at an electronic device with a touch-sensitive display: receiving a user input, the user input is one or more input points applied to the touch-sensitive display;creating an event object in response to the user input;determining whether the event object invokes a scroll or gesture operation by distinguishing between the user input consisting of a single input point that moves a distance across the touch-sensitive display that is interpreted as the scroll operation, and the user input consisting of a plurality of input points applied to the touch-sensitive display that are interpreted as the gesture operation; andissuing at least one scroll or gesture call based on invoking the scroll or gesture operation, wherein the gesture operation is at least one of a scaling operation and a rotating operation.
14. The method of claim 13, further comprising: while the scroll operation is invoked: in accordance with a determination that an angle formed by the user input with a horizontal line on the touch-sensitive display is less than a threshold angle, locking the scrolling in a horizontal direction; andin accordance with a determination that an angle formed by the user input with a vertical line on the touch-sensitive display is less than the threshold angle, locking the scrolling in a vertical direction.
15. The method of claim 13, further comprising: while the scroll operation is invoked: scrolling a window associated with the event object;rubberbanding a scrolled region of the window by a predetermined maximum displacement value as the scrolled region exceeds an edge of the window; andbouncing the scrolled region in an opposite direction of the scroll in response to termination of the user input.
16. The method of claim 13, further comprising: while the scaling operation is invoked: scaling a view associated with the event object while maintaining a center of the view as a center of the scaled view.
17. The method of claim 13, further comprising: while the scaling operation is invoked: scaling a view associated with the event object based on a scale factor that is within a range of a minimum scale factor and a maximum scale factor, the minimum and maximum scale factors being associated with the event object, wherein the scale factor is determined based on movement of the plurality of input points of the user input on the touch-sensitive display.
18. The method of claim 13, further comprising: while the rotating operation is invoked: rotating a view associated with the event object by a rotation angle that is within a range of a minimum rotation angle and a maximum rotation angle, the minimum and maximum rotation angles being associated with the event object, wherein the rotation angle is determined based on movement of the plurality of input points of the user input on the touch-sensitive display.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 14/189,922, filed Feb. 25, 2014, now U.S. Pat. No. 9,037,995, issued on May 19, 2015, which is a continuation of U.S. application Ser. No. 13/867,950, filed Apr. 22, 2013, now U.S. Pat. No. 8,661,363, issued on Feb. 25, 2014, which is a continuation of U.S. patent application Ser. No. 12/869,182, filed Aug. 26, 2010, now U.S. Pat. No. 8,429,557, issued Apr. 23, 2013, which is a divisional of U.S. patent application Ser. No. 11/620,717, filed Jan. 7, 2007, now U.S. Pat. No. 7,844,915, issued Nov. 30, 2010, all of which are incorporated herein by reference in their entirety.

US Referenced Citations (694)

Number	Name	Date	Kind
3825730	Worthington, Jr. et al.	Jul 1974	A
3846826	Mueller	Nov 1974	A
4014000	Uno et al.	Mar 1977	A
4146924	Birk et al.	Mar 1979	A
4219847	Pinkney et al.	Aug 1980	A
4290052	Eichelberger et al.	Sep 1981	A
4305071	Bell et al.	Dec 1981	A
4305131	Best	Dec 1981	A
4340911	Kato et al.	Jul 1982	A
4346376	Mallos	Aug 1982	A
4375674	Thornton	Mar 1983	A
4396945	Dimatteo et al.	Aug 1983	A
4435835	Sakow et al.	Mar 1984	A
4455452	Schuyler	Jun 1984	A
4475122	Green	Oct 1984	A
4484179	Kasday	Nov 1984	A
4526043	Boie et al.	Jul 1985	A
4542375	Alles et al.	Sep 1985	A
4550221	Mabusth	Oct 1985	A
4561017	Greene	Dec 1985	A
4613942	Chen	Sep 1986	A
4618989	Tsukune et al.	Oct 1986	A
4629319	Clarke et al.	Dec 1986	A
4631525	Serravalle	Dec 1986	A
4631676	Pugh	Dec 1986	A
4644100	Brenner et al.	Feb 1987	A
4654872	Hisano et al.	Mar 1987	A
4686332	Greanias et al.	Aug 1987	A
4686374	Liptay-Wagner et al.	Aug 1987	A
4710760	Kasday	Dec 1987	A
4746770	Mcavinney	May 1988	A
4755811	Slavin et al.	Jul 1988	A
4763356	Day et al.	Aug 1988	A
4787040	Ames et al.	Nov 1988	A
4806709	Evans	Feb 1989	A
4839634	More et al.	Jun 1989	A
4843568	Krueger et al.	Jun 1989	A
4914624	Dunthorn	Apr 1990	A
4954967	Takahashi	Sep 1990	A
4988981	Zimmerman et al.	Jan 1991	A
5045843	Hansen	Sep 1991	A
5046434	Breezer et al.	Sep 1991	A
5072294	Engle	Dec 1991	A
5073950	Colbert et al.	Dec 1991	A
5105186	May	Apr 1992	A
5113041	Blonder et al.	May 1992	A
5119079	Hube et al.	Jun 1992	A
5153829	Furuya et al.	Oct 1992	A
5168531	Sigel	Dec 1992	A
5186629	Rohen	Feb 1993	A
5203704	Mccloud	Apr 1993	A
5223547	Harada et al.	Jun 1993	A
5227985	Dementhon	Jul 1993	A
5231381	Duwaer	Jul 1993	A
5233547	Kapp et al.	Aug 1993	A
5235509	Mueller et al.	Aug 1993	A
5252951	Tannenbaum et al.	Oct 1993	A
5267327	Hirayama	Nov 1993	A
RE34476	Norwood	Dec 1993	E
5276794	Lamb, Jr.	Jan 1994	A
5293430	Shiau et al.	Mar 1994	A
5297030	Vassigh et al.	Mar 1994	A
5327161	Logan et al.	Jul 1994	A
5335557	Yasutake	Aug 1994	A
5341133	Savoy et al.	Aug 1994	A
5374787	Miller et al.	Dec 1994	A
5412189	Cragun	May 1995	A
5418760	Kawashima et al.	May 1995	A
5428367	Mikan	Jun 1995	A
5454960	Newsom	Oct 1995	A
5459793	Naoi et al.	Oct 1995	A
5463388	Boie et al.	Oct 1995	A
5463725	Henckel et al.	Oct 1995	A
5468947	Danielson et al.	Nov 1995	A
5479528	Speeter	Dec 1995	A
5483261	Yasutake	Jan 1996	A
5488204	Mead et al.	Jan 1996	A
5491495	Ward et al.	Feb 1996	A
5495269	Elrod et al.	Feb 1996	A
5495566	Kwatinetz	Feb 1996	A
5511148	Wellner	Apr 1996	A
5513309	Meier et al.	Apr 1996	A
5528266	Arbeitman et al.	Jun 1996	A
5530456	Kokubo	Jun 1996	A
5534893	Hansen et al.	Jul 1996	A
5543588	Bisset et al.	Aug 1996	A
5543591	Gillespie et al.	Aug 1996	A
5552787	Schuler et al.	Sep 1996	A
5559301	Bryan et al.	Sep 1996	A
5566337	Szymanski et al.	Oct 1996	A
5570113	Zetts	Oct 1996	A
5572239	Jaeger	Nov 1996	A
5581243	Ouellette et al.	Dec 1996	A
5583543	Takahashi et al.	Dec 1996	A
5589856	Stein et al.	Dec 1996	A
5594806	Colbert	Jan 1997	A
5603053	Gough et al.	Feb 1997	A
5627567	Davidson	May 1997	A
5627959	Brown et al.	May 1997	A
5638093	Takahashi et al.	Jun 1997	A
5655094	Cline et al.	Aug 1997	A
5676064	Shuert	Oct 1997	A
5686940	Kuga	Nov 1997	A
5708460	Young et al.	Jan 1998	A
5709219	Chen et al.	Jan 1998	A
5712661	Jaeger	Jan 1998	A
5726685	Kuth et al.	Mar 1998	A
5729249	Yasutake	Mar 1998	A
5734742	Asaeda et al.	Mar 1998	A
5745116	Pisutha-Arnond	Apr 1998	A
5749908	Snell	May 1998	A
5764218	Della et al.	Jun 1998	A
5798752	Buxton et al.	Aug 1998	A
5805144	Scholder et al.	Sep 1998	A
5805145	Jaeger	Sep 1998	A
5805146	Jaeger et al.	Sep 1998	A
5805161	Tiphane	Sep 1998	A
5809166	Huang et al.	Sep 1998	A
5818455	Stone et al.	Oct 1998	A
5825352	Bisset et al.	Oct 1998	A
5835079	Shieh	Nov 1998	A
5838302	Kuriyama et al.	Nov 1998	A
5841428	Jaeger et al.	Nov 1998	A
5844547	Minakuchi et al.	Dec 1998	A
5850358	Danielson et al.	Dec 1998	A
5856822	Du et al.	Jan 1999	A
5859631	Bergman et al.	Jan 1999	A
5864636	Chisaka	Jan 1999	A
5867149	Jaeger	Feb 1999	A
5867158	Murasaki et al.	Feb 1999	A
5869791	Young	Feb 1999	A
5871251	Welling et al.	Feb 1999	A
5880411	Gillespie et al.	Mar 1999	A
5898434	Small et al.	Apr 1999	A
5903902	Orr et al.	May 1999	A
5917477	Lee	Jun 1999	A
5923319	Bishop et al.	Jul 1999	A
5936613	Jaeger et al.	Aug 1999	A
5942733	Allen et al.	Aug 1999	A
5943043	Furuhata et al.	Aug 1999	A
5943052	Allen et al.	Aug 1999	A
5949345	Beckert et al.	Sep 1999	A
5956020	D'Amico et al.	Sep 1999	A
5982355	Jaeger et al.	Nov 1999	A
5995104	Kataoka et al.	Nov 1999	A
6002808	Freeman	Dec 1999	A
6008800	Pryor	Dec 1999	A
6016355	Dickinson et al.	Jan 2000	A
6028271	Gillespie et al.	Feb 2000	A
6028602	Weidenfeller et al.	Feb 2000	A
6029214	Dorfman et al.	Feb 2000	A
6034688	Greenwood et al.	Mar 2000	A
6035343	Tsushima et al.	Mar 2000	A
6037882	Levy	Mar 2000	A
6037937	Beaton et al.	Mar 2000	A
6057540	Gordon et al.	May 2000	A
6061063	Wagner et al.	May 2000	A
6066075	Poulton	May 2000	A
6067068	Hussain	May 2000	A
6089371	Lin	Jul 2000	A
6100874	Schena et al.	Aug 2000	A
6111577	Zilles et al.	Aug 2000	A
6121960	Carroll et al.	Sep 2000	A
6141018	Beri et al.	Oct 2000	A
6169538	Nowlan et al.	Jan 2001	B1
6175610	Peter	Jan 2001	B1
6188391	Seely et al.	Feb 2001	B1
6208329	Ballare	Mar 2001	B1
6219035	Skog	Apr 2001	B1
6222465	Kumar et al.	Apr 2001	B1
6239389	Allen et al.	May 2001	B1
6255604	Tokioka et al.	Jul 2001	B1
6256020	Pabon et al.	Jul 2001	B1
6259436	Moon et al.	Jul 2001	B1
6262717	Donohue et al.	Jul 2001	B1
6278441	Gouzman et al.	Aug 2001	B1
6278443	Amro et al.	Aug 2001	B1
6310610	Beaton et al.	Oct 2001	B1
6311162	Reichwein et al.	Oct 2001	B1
6313849	Takase et al.	Nov 2001	B1
6313853	Lamontagne et al.	Nov 2001	B1
6323846	Westerman et al.	Nov 2001	B1
6330009	Murasaki et al.	Dec 2001	B1
6337698	Keely et al.	Jan 2002	B1
6369821	Merrill et al.	Apr 2002	B2
6380929	Platt	Apr 2002	B1
6393401	Loudermilk et al.	May 2002	B1
6414672	Rekimoto et al.	Jul 2002	B2
6421042	Omura et al.	Jul 2002	B1
6421046	Edgren	Jul 2002	B1
6429846	Rosenberg et al.	Aug 2002	B2
6441806	Jaeger	Aug 2002	B1
6446083	Leight et al.	Sep 2002	B1
6466203	Van Ee	Oct 2002	B2
6486896	Ubillos	Nov 2002	B1
6489951	Wong et al.	Dec 2002	B1
6492979	Kent et al.	Dec 2002	B1
6498590	Dietz et al.	Dec 2002	B1
6504530	Wilson et al.	Jan 2003	B1
6509907	Kuwabara	Jan 2003	B1
6538635	Ringot	Mar 2003	B1
6552719	Lui et al.	Apr 2003	B2
6559869	Lui et al.	May 2003	B1
6563492	Furuya	May 2003	B1
6567102	Kung	May 2003	B2
6570557	Westerman et al.	May 2003	B1
6570594	Wagner	May 2003	B1
6590595	Wagner et al.	Jul 2003	B1
6597347	Yasutake	Jul 2003	B1
6636242	Bowman-Amuah	Oct 2003	B2
6639584	Li	Oct 2003	B1
6657615	Harada	Dec 2003	B2
6661409	Demartines et al.	Dec 2003	B2
6664982	Bi	Dec 2003	B1
6664989	Snyder et al.	Dec 2003	B1
6677932	Westerman	Jan 2004	B1
6677965	Ullmann et al.	Jan 2004	B1
6683628	Nakagawa et al.	Jan 2004	B1
6690365	Hinckley et al.	Feb 2004	B2
6690387	Zimmerman et al.	Feb 2004	B2
6707449	Hinckley et al.	Mar 2004	B2
6714221	Christie et al.	Mar 2004	B1
6714936	Nevin, III	Mar 2004	B1
6720949	Pryor et al.	Apr 2004	B1
6727891	Moriya et al.	Apr 2004	B2
6735583	Bjarnestam et al.	May 2004	B1
6741996	Brechner et al.	May 2004	B1
6750848	Pryor	Jun 2004	B1
6757673	Makus et al.	Jun 2004	B2
6765557	Segal et al.	Jul 2004	B1
6778992	Searle et al.	Aug 2004	B1
6788815	Lui et al.	Sep 2004	B2
6791530	Vernier et al.	Sep 2004	B2
6809724	Shiraishi et al.	Oct 2004	B1
6820237	Abu-Hakima et al.	Nov 2004	B1
6831631	Chuang	Dec 2004	B2
6839721	Schwols	Jan 2005	B2
6856259	Sharp	Feb 2005	B1
6856326	Zhai	Feb 2005	B1
6888532	Wong et al.	May 2005	B2
6888536	Westerman et al.	May 2005	B2
6903927	Anlauff	Jun 2005	B2
6907575	Duarte	Jun 2005	B2
6912462	Ogaki	Jun 2005	B2
6920619	Milekic	Jul 2005	B1
6924790	Bi	Aug 2005	B1
6938222	Hullender et al.	Aug 2005	B2
6957392	Simister et al.	Oct 2005	B2
6958749	Matsushita et al.	Oct 2005	B1
6963937	Kamper et al.	Nov 2005	B1
6970160	Mulligan et al.	Nov 2005	B2
6972749	Hinckley et al.	Dec 2005	B2
6972776	Davis et al.	Dec 2005	B2
6975306	Hinckley et al.	Dec 2005	B2
6985137	Kaikuranta	Jan 2006	B2
6985178	Morita et al.	Jan 2006	B1
7009599	Pihlaja	Mar 2006	B2
7009626	Anwar	Mar 2006	B2
7013435	Gallo et al.	Mar 2006	B2
7015894	Morohoshi	Mar 2006	B2
7023427	Kraus et al.	Apr 2006	B2
7030860	Hsu et al.	Apr 2006	B1
7030861	Westerman et al.	Apr 2006	B1
7030862	Nozaki	Apr 2006	B2
7046230	Zadesky et al.	May 2006	B2
7061474	Hinckley et al.	Jun 2006	B2
7075512	Fabre et al.	Jul 2006	B1
7081886	Nakano et al.	Jul 2006	B2
7084859	Pryor	Aug 2006	B1
7088374	David et al.	Aug 2006	B2
7102626	Denny, III	Sep 2006	B2
7109978	Gillespie et al.	Sep 2006	B2
7117453	Drucker et al.	Oct 2006	B2
7138983	Wakai et al.	Nov 2006	B2
7152210	Van Den Hoven et al.	Dec 2006	B1
7154534	Seki et al.	Dec 2006	B2
7155048	Ohara	Dec 2006	B2
7173623	Calkins et al.	Feb 2007	B2
7180500	Marvit et al.	Feb 2007	B2
7181373	Le Cocq et al.	Feb 2007	B2
7184064	Zimmerman et al.	Feb 2007	B2
7184796	Karidis et al.	Feb 2007	B2
7202857	Hinckley et al.	Apr 2007	B2
7240291	Card et al.	Jul 2007	B2
7254775	Geaghan et al.	Aug 2007	B2
7256767	Wong et al.	Aug 2007	B2
7283126	Leung	Oct 2007	B2
7337412	Guido et al.	Feb 2008	B2
RE40153	Westerman et al.	Mar 2008	E
7339580	Westerman et al.	Mar 2008	B2
7346850	Swartz et al.	Mar 2008	B2
7355620	Ikehata et al.	Apr 2008	B2
7382139	Mackey	Jun 2008	B2
7385592	Collins	Jun 2008	B2
7411575	Hill et al.	Aug 2008	B2
7446783	Grossman	Nov 2008	B2
7450113	Gillespie et al.	Nov 2008	B2
7450114	Anwar	Nov 2008	B2
7469381	Ording	Dec 2008	B2
7479949	Jobs et al.	Jan 2009	B2
7487447	Jerger	Feb 2009	B1
7499027	Brigham et al.	Mar 2009	B2
7508375	Liu	Mar 2009	B2
7511702	Hotelling	Mar 2009	B2
7532205	Gillespie et al.	May 2009	B2
7561159	Abel et al.	Jul 2009	B2
7564448	Yi	Jul 2009	B2
7576732	Lii	Aug 2009	B2
7598949	Han	Oct 2009	B2
7612786	Vale et al.	Nov 2009	B2
7614008	Ording	Nov 2009	B2
7614019	Rimas Ribikauskas et al.	Nov 2009	B2
7653883	Hotelling et al.	Jan 2010	B2
7658675	Hotta	Feb 2010	B2
7663607	Hotelling et al.	Feb 2010	B2
7673255	Schechter et al.	Mar 2010	B2
7701442	Wong et al.	Apr 2010	B2
7719523	Hillis	May 2010	B2
7724242	Hillis et al.	May 2010	B2
7728821	Hillis et al.	Jun 2010	B2
7735016	Celik et al.	Jun 2010	B2
7750893	Hashimoto et al.	Jul 2010	B2
7786975	Ording et al.	Aug 2010	B2
7812826	Ording et al.	Oct 2010	B2
7839391	Varian et al.	Nov 2010	B2
7843427	Ording et al.	Nov 2010	B2
7843429	Pryor	Nov 2010	B2
7844913	Amano et al.	Nov 2010	B2
7844915	Platzer et al.	Nov 2010	B2
7864037	Miller	Jan 2011	B2
7872640	Lira	Jan 2011	B2
7872652	Platzer et al.	Jan 2011	B2
7900156	Andre	Mar 2011	B2
7903115	Platzer et al.	Mar 2011	B2
7907124	Hillis et al.	Mar 2011	B2
7907125	Weiss et al.	Mar 2011	B2
7917584	Arthursson	Mar 2011	B2
7924271	Christie et al.	Apr 2011	B2
7925996	Hofmeister et al.	Apr 2011	B2
7941760	Kocienda et al.	May 2011	B2
7956847	Christie	Jun 2011	B2
7962862	Kulp et al.	Jun 2011	B2
7966578	Tolmasky et al.	Jun 2011	B2
7995030	Joung et al.	Aug 2011	B2
8051406	Knight et al.	Nov 2011	B2
8091045	Christie et al.	Jan 2012	B2
8112299	Kim et al.	Feb 2012	B2
8115744	Kong et al.	Feb 2012	B2
8135171	Ho et al.	Mar 2012	B2
8140570	Ingrassia et al.	Mar 2012	B2
8171432	Matas et al.	May 2012	B2
8174502	Bolsinga et al.	May 2012	B2
8214768	Boule et al.	Jul 2012	B2
8239784	Hotelling et al.	Aug 2012	B2
8253695	Ganatra et al.	Aug 2012	B2
8285499	Moore et al.	Oct 2012	B2
8289289	Rimon et al.	Oct 2012	B2
8291344	Chaudhri	Oct 2012	B2
8296332	Boley et al.	Oct 2012	B2
8310459	Nurmi	Nov 2012	B2
8314775	Westerman et al.	Nov 2012	B2
8428893	Moore et al.	Apr 2013	B2
8489783	Wilson	Jul 2013	B2
8560975	Beaver et al.	Oct 2013	B2
8566044	Shaffer et al.	Oct 2013	B2
8566045	Shaffer et al.	Oct 2013	B2
8570277	Rekimoto	Oct 2013	B2
8645827	Beaver et al.	Feb 2014	B2
8682602	Moore et al.	Mar 2014	B2
20010009033	Morisaki et al.	Jul 2001	A1
20010011998	Agata et al.	Aug 2001	A1
20010012001	Rekimoto et al.	Aug 2001	A1
20010028369	Gallo et al.	Oct 2001	A1
20010035880	Musatov et al.	Nov 2001	A1
20010045949	Chithambaram et al.	Nov 2001	A1
20020015024	Westerman et al.	Feb 2002	A1
20020015064	Robotham et al.	Feb 2002	A1
20020018051	Singh	Feb 2002	A1
20020036618	Wakai et al.	Mar 2002	A1
20020056575	Keely et al.	May 2002	A1
20020067346	Mouton	Jun 2002	A1
20020130839	Wallace et al.	Sep 2002	A1
20020158838	Smith et al.	Oct 2002	A1
20020191029	Gillespie et al.	Dec 2002	A1
20020194589	Cristofalo et al.	Dec 2002	A1
20030016252	Noy et al.	Jan 2003	A1
20030071850	Geidl	Apr 2003	A1
20030071858	Morohoshi	Apr 2003	A1
20030080946	Chuang	May 2003	A1
20030085870	Hinckley	May 2003	A1
20030095096	Robbin et al.	May 2003	A1
20030095135	Kaasila et al.	May 2003	A1
20030095697	Wood et al.	May 2003	A1
20030122787	Zimmerman et al.	Jul 2003	A1
20030132959	Simister et al.	Jul 2003	A1
20030146941	Bailey et al.	Aug 2003	A1
20030159567	Subotnick	Aug 2003	A1
20030160832	Ridgley et al.	Aug 2003	A1
20030167119	Cherveny	Sep 2003	A1
20030174149	Fujisaki et al.	Sep 2003	A1
20030184525	Tsai	Oct 2003	A1
20030184593	Dunlop	Oct 2003	A1
20030193481	Sokolsky	Oct 2003	A1
20030197689	May	Oct 2003	A1
20030210258	Williams	Nov 2003	A1
20030222917	Trantow	Dec 2003	A1
20030231168	Bell et al.	Dec 2003	A1
20040001627	Simmons et al.	Jan 2004	A1
20040012572	Sowden et al.	Jan 2004	A1
20040021676	Chen et al.	Feb 2004	A1
20040021694	Doar	Feb 2004	A1
20040021698	Baldwin et al.	Feb 2004	A1
20040027398	Jaeger	Feb 2004	A1
20040034801	Jaeger	Feb 2004	A1
20040039474	Kontani	Feb 2004	A1
20040056837	Koga et al.	Mar 2004	A1
20040070573	Graham	Apr 2004	A1
20040080541	Saiga et al.	Apr 2004	A1
20040095387	Demsey et al.	May 2004	A1
20040100479	Nakano et al.	May 2004	A1
20040108995	Hoshino et al.	Jun 2004	A1
20040119700	Ichikawa	Jun 2004	A1
20040125136	Wallenius	Jul 2004	A1
20040135817	Daughtery et al.	Jul 2004	A1
20040155888	Padgitt et al.	Aug 2004	A1
20040160419	Padgitt	Aug 2004	A1
20040160420	Baharav et al.	Aug 2004	A1
20040161132	Cohen et al.	Aug 2004	A1
20040167919	Sterling et al.	Aug 2004	A1
20040189720	Wilson et al.	Sep 2004	A1
20040210847	Berson et al.	Oct 2004	A1
20040215643	Brechner et al.	Oct 2004	A1
20040222992	Calkins et al.	Nov 2004	A1
20040224638	Fadell et al.	Nov 2004	A1
20040263486	Seni	Dec 2004	A1
20050005241	Hunleth et al.	Jan 2005	A1
20050008343	Frohlich et al.	Jan 2005	A1
20050012723	Pallakoff	Jan 2005	A1
20050017957	Yi	Jan 2005	A1
20050024341	Gillespie et al.	Feb 2005	A1
20050027666	Beck et al.	Feb 2005	A1
20050030255	Chiu et al.	Feb 2005	A1
20050041385	Kikinis et al.	Feb 2005	A1
20050046621	Kaikuranta	Mar 2005	A1
20050052427	Wu et al.	Mar 2005	A1
20050057524	Hill et al.	Mar 2005	A1
20050088418	Nguyen	Apr 2005	A1
20050088443	Blanco et al.	Apr 2005	A1
20050093868	Hinckley	May 2005	A1
20050110769	Dacosta et al.	May 2005	A1
20050114788	Fabritius	May 2005	A1
20050122806	Arakawa et al.	Jun 2005	A1
20050145807	Lapstun et al.	Jul 2005	A1
20050162402	Watanachote	Jul 2005	A1
20050168353	Dement et al.	Aug 2005	A1
20050168488	Montague	Aug 2005	A1
20050179648	Barabe et al.	Aug 2005	A1
20050183035	Ringel et al.	Aug 2005	A1
20050190144	Kong	Sep 2005	A1
20050193015	Logston et al.	Sep 2005	A1
20050193351	Huoviala	Sep 2005	A1
20050195154	Robbins et al.	Sep 2005	A1
20050198588	Lin et al.	Sep 2005	A1
20050210419	Kela et al.	Sep 2005	A1
20050212754	Marvit et al.	Sep 2005	A1
20050237308	Autio et al.	Oct 2005	A1
20050268247	Baneth	Dec 2005	A1
20050270269	Tokkonen	Dec 2005	A1
20050275618	Juh et al.	Dec 2005	A1
20050275636	Dehlin et al.	Dec 2005	A1
20060001650	Robbins et al.	Jan 2006	A1
20060001652	Chiu et al.	Jan 2006	A1
20060007174	Shen	Jan 2006	A1
20060007176	Shen	Jan 2006	A1
20060007178	Davis	Jan 2006	A1
20060010400	Dehlin et al.	Jan 2006	A1
20060022955	Kennedy	Feb 2006	A1
20060022956	Lengeling et al.	Feb 2006	A1
20060025218	Hotta	Feb 2006	A1
20060026521	Hotelling et al.	Feb 2006	A1
20060026535	Hotelling et al.	Feb 2006	A1
20060026536	Hotelling et al.	Feb 2006	A1
20060026676	O'Donoghue	Feb 2006	A1
20060028428	Dai et al.	Feb 2006	A1
20060028455	Hinckley et al.	Feb 2006	A1
20060031786	Hillis et al.	Feb 2006	A1
20060033751	Keely et al.	Feb 2006	A1
20060036955	Baudisch et al.	Feb 2006	A1
20060038796	Hinckley et al.	Feb 2006	A1
20060044259	Hotelling et al.	Mar 2006	A1
20060047386	Kanevsky et al.	Mar 2006	A1
20060048073	Jarrett et al.	Mar 2006	A1
20060049920	Sadler et al.	Mar 2006	A1
20060055662	Rimas-Ribikauskas et al.	Mar 2006	A1
20060055669	Das	Mar 2006	A1
20060061551	Fateh	Mar 2006	A1
20060066588	Lyon et al.	Mar 2006	A1
20060077183	Studt	Apr 2006	A1
20060077544	Stark	Apr 2006	A1
20060082549	Hoshino et al.	Apr 2006	A1
20060084852	Mason et al.	Apr 2006	A1
20060092142	Gillespie et al.	May 2006	A1
20060094502	Katayama et al.	May 2006	A1
20060097991	Hotelling et al.	May 2006	A1
20060101354	Hashimoto et al.	May 2006	A1
20060112335	Hofmeister et al.	May 2006	A1
20060123353	Matthews et al.	Jun 2006	A1
20060125799	Hillis et al.	Jun 2006	A1
20060125803	Westerman et al.	Jun 2006	A1
20060132460	Kolmykov-Zotov et al.	Jun 2006	A1
20060136833	Dettinger et al.	Jun 2006	A1
20060156249	Blythe et al.	Jul 2006	A1
20060161871	Hotelling et al.	Jul 2006	A1
20060164399	Cheston et al.	Jul 2006	A1
20060181510	Faith	Aug 2006	A1
20060181519	Vernier et al.	Aug 2006	A1
20060187215	Rosenberg et al.	Aug 2006	A1
20060190833	Sangiovanni et al.	Aug 2006	A1
20060197753	Hotelling	Sep 2006	A1
20060202953	Pryor et al.	Sep 2006	A1
20060210958	Rimas-Ribikauskas et al.	Sep 2006	A1
20060227116	Zotov et al.	Oct 2006	A1
20060236263	Bathiche et al.	Oct 2006	A1
20060238495	Davis	Oct 2006	A1
20060242602	Schechter et al.	Oct 2006	A1
20060242607	Hudson	Oct 2006	A1
20060250377	Zadesky et al.	Nov 2006	A1
20060253793	Zhai et al.	Nov 2006	A1
20060267959	Goto et al.	Nov 2006	A1
20060279548	Geaghan	Dec 2006	A1
20060284792	Foxlin	Dec 2006	A1
20060288313	Hillis	Dec 2006	A1
20060294472	Cheng et al.	Dec 2006	A1
20070008066	Fukuda	Jan 2007	A1
20070013697	Gilboa	Jan 2007	A1
20070024646	Saarinen et al.	Feb 2007	A1
20070028191	Tsuji	Feb 2007	A1
20070035513	Sherrard et al.	Feb 2007	A1
20070036346	Kwon	Feb 2007	A1
20070046643	Hillis et al.	Mar 2007	A1
20070046646	Kwon et al.	Mar 2007	A1
20070050469	Gupta et al.	Mar 2007	A1
20070055967	Poff et al.	Mar 2007	A1
20070061126	Russo et al.	Mar 2007	A1
20070064004	Bonner et al.	Mar 2007	A1
20070064869	Albert	Mar 2007	A1
20070067745	Choi et al.	Mar 2007	A1
20070075965	Huppi et al.	Apr 2007	A1
20070081726	Westerman et al.	Apr 2007	A1
20070089069	Hsieh et al.	Apr 2007	A1
20070109275	Chuang	May 2007	A1
20070109279	Sigona	May 2007	A1
20070120835	Sato	May 2007	A1
20070132789	Ording et al.	Jun 2007	A1
20070146337	Ording et al.	Jun 2007	A1
20070149252	Jobs et al.	Jun 2007	A1
20070150826	Anzures et al.	Jun 2007	A1
20070150842	Chaudhri et al.	Jun 2007	A1
20070152976	Townsend et al.	Jul 2007	A1
20070152978	Kocienda et al.	Jul 2007	A1
20070152979	Jobs et al.	Jul 2007	A1
20070152984	Ording et al.	Jul 2007	A1
20070155434	Jobs et al.	Jul 2007	A1
20070156364	Rothkopf	Jul 2007	A1
20070157089	Van Os et al.	Jul 2007	A1
20070157094	Lemay et al.	Jul 2007	A1
20070174257	Howard	Jul 2007	A1
20070176903	Dahlin et al.	Aug 2007	A1
20070177803	Elias et al.	Aug 2007	A1
20070177804	Elias et al.	Aug 2007	A1
20070185876	Mendis et al.	Aug 2007	A1
20070198926	Joguet et al.	Aug 2007	A1
20070214462	Boillot	Sep 2007	A1
20070236475	Wherry	Oct 2007	A1
20070242056	Engelhardt et al.	Oct 2007	A1
20070242607	Sadler et al.	Oct 2007	A1
20070247435	Benko et al.	Oct 2007	A1
20070247442	Andre et al.	Oct 2007	A1
20070252821	Hollemans et al.	Nov 2007	A1
20070256026	Klassen et al.	Nov 2007	A1
20070257891	Esenther et al.	Nov 2007	A1
20070262964	Zotov et al.	Nov 2007	A1
20070277124	Shin et al.	Nov 2007	A1
20070288856	Butlin et al.	Dec 2007	A1
20070291009	Wright et al.	Dec 2007	A1
20080001923	Hall et al.	Jan 2008	A1
20080005703	Radivojevic et al.	Jan 2008	A1
20080012835	Rimon et al.	Jan 2008	A1
20080016096	Wilding et al.	Jan 2008	A1
20080028327	Hirota et al.	Jan 2008	A1
20080034029	Fang et al.	Feb 2008	A1
20080036743	Westerman et al.	Feb 2008	A1
20080043020	Snow et al.	Feb 2008	A1
20080046425	Perski	Feb 2008	A1
20080048978	Trent et al.	Feb 2008	A1
20080052945	Matas et al.	Mar 2008	A1
20080062207	Park	Mar 2008	A1
20080084400	Rosenberg	Apr 2008	A1
20080088602	Hotelling	Apr 2008	A1
20080094356	Ording et al.	Apr 2008	A1
20080094368	Ording et al.	Apr 2008	A1
20080094369	Ganatra et al.	Apr 2008	A1
20080094370	Ording et al.	Apr 2008	A1
20080104544	Collins et al.	May 2008	A1
20080114614	Mahesh et al.	May 2008	A1
20080120576	Kariathungal et al.	May 2008	A1
20080158191	Yang et al.	Jul 2008	A1
20080162751	Wilson	Jul 2008	A1
20080165132	Weiss et al.	Jul 2008	A1
20080165136	Christie et al.	Jul 2008	A1
20080165140	Christie et al.	Jul 2008	A1
20080165141	Christie	Jul 2008	A1
20080165160	Kocienda et al.	Jul 2008	A1
20080168388	Decker	Jul 2008	A1
20080168395	Ording et al.	Jul 2008	A1
20080168402	Blumenberg	Jul 2008	A1
20080168404	Ording	Jul 2008	A1
20080168405	Tolmasky et al.	Jul 2008	A1
20080172633	Jeon et al.	Jul 2008	A1
20080180404	Han et al.	Jul 2008	A1
20080204426	Hotelling et al.	Aug 2008	A1
20080207130	Kunii	Aug 2008	A1
20080218489	Park et al.	Sep 2008	A1
20080231610	Hotelling et al.	Sep 2008	A1
20080284925	Han	Nov 2008	A1
20090049388	Taib et al.	Feb 2009	A1
20090051671	Konstas	Feb 2009	A1
20090058830	Herz et al.	Mar 2009	A1
20090064047	Shim et al.	Mar 2009	A1
20090207140	Hansson	Aug 2009	A1
20090211891	Lai et al.	Aug 2009	A1
20090225037	Williamson et al.	Sep 2009	A1
20090225038	Bolsinga et al.	Sep 2009	A1
20090225039	Williamson et al.	Sep 2009	A1
20090228828	Beatty et al.	Sep 2009	A1
20090228901	Beaver et al.	Sep 2009	A1
20090231281	Whytock et al.	Sep 2009	A1
20090244020	Sjolin	Oct 2009	A1
20090251434	Rimon et al.	Oct 2009	A1
20090259969	Pallakoff	Oct 2009	A1
20090262087	Kim	Oct 2009	A1
20090273571	Bowens	Nov 2009	A1
20090282332	Porat	Nov 2009	A1
20090284479	Dennis et al.	Nov 2009	A1
20090307623	Agarawala et al.	Dec 2009	A1
20090309847	Russell et al.	Dec 2009	A1
20090322687	Duncan et al.	Dec 2009	A1
20090322699	Hansson	Dec 2009	A1
20090322700	D'Souza et al.	Dec 2009	A1
20100013676	Do et al.	Jan 2010	A1
20100020025	Lemort et al.	Jan 2010	A1
20100020221	Tupman et al.	Jan 2010	A1
20100030612	Kim et al.	Feb 2010	A1
20100046850	Ho et al.	Feb 2010	A1
20100085323	Bogue	Apr 2010	A1
20100107116	Rieman et al.	Apr 2010	A1
20100146458	Wadekar	Jun 2010	A1
20100149122	Lin	Jun 2010	A1
20100156804	Young	Jun 2010	A1
20100172624	Watts	Jul 2010	A1
20100177053	Yasutake	Jul 2010	A2
20100182248	Chun	Jul 2010	A1
20100235118	Moore et al.	Sep 2010	A1
20100245267	Min et al.	Sep 2010	A1
20100267449	Gagner et al.	Oct 2010	A1
20100281435	Bangalore et al.	Nov 2010	A1
20100283739	Zhang et al.	Nov 2010	A1
20100299594	Zalewski et al.	Nov 2010	A1
20100325575	Platzer et al.	Dec 2010	A1
20110037714	Seo et al.	Feb 2011	A1
20110047459	Van Der Westhuizen	Feb 2011	A1
20110069021	Hill	Mar 2011	A1
20110090257	Ko et al.	Apr 2011	A1
20110102336	Seok et al.	May 2011	A1
20110115745	Cabrera Cordon et al.	May 2011	A1
20110167391	Momeyer et al.	Jul 2011	A1
20110179380	Shaffer et al.	Jul 2011	A1
20110179386	Shaffer et al.	Jul 2011	A1
20110179387	Shaffer et al.	Jul 2011	A1
20110181526	Shaffer et al.	Jul 2011	A1
20110252306	Williamson et al.	Oct 2011	A1
20110252307	Williamson et al.	Oct 2011	A1
20110252368	Anzures et al.	Oct 2011	A1
20110291951	Tong	Dec 2011	A1
20110295596	Hung et al.	Dec 2011	A1
20110310046	Beaver et al.	Dec 2011	A1
20110310047	Moore et al.	Dec 2011	A1
20110314430	Blumenberg	Dec 2011	A1
20110321125	Kyohgoku et al.	Dec 2011	A1
20120023509	Blumenberg	Jan 2012	A1
20120278725	Gordon et al.	Nov 2012	A1
20130009986	Shah et al.	Jan 2013	A1
20130016039	Moore et al.	Jan 2013	A1
20130069899	Beaver et al.	Mar 2013	A1

Foreign Referenced Citations (137)

Number	Date	Country
2007283771	Apr 2008	AU
2755443	Sep 2010	CA
1326564	Dec 2001	CN
1422481	Jun 2003	CN
1695105	Nov 2005	CN
1704886	Dec 2005	CN
1754141	Mar 2006	CN
1797308	Jul 2006	CN
1841284	Oct 2006	CN
1845046	Oct 2006	CN
1860429	Nov 2006	CN
1967458	May 2007	CN
101410781	Apr 2009	CN
101526880	Sep 2009	CN
10172740	Jun 2010	CN
102008052485	Apr 2010	DE
269364	Jun 1988	EP
450196	Oct 1991	EP
0538705	Jul 1993	EP
0609021	Aug 1994	EP
0622722	Nov 1994	EP
0626635	Nov 1994	EP
0635779	Jan 1995	EP
0701220	Mar 1996	EP
0712825	May 1996	EP
0725331	Aug 1996	EP
0827064	Mar 1998	EP
0827094	Mar 1998	EP
0880091	Nov 1998	EP
0944218	Sep 1999	EP
1517228	Mar 2005	EP
2031837	Mar 2009	EP
2102738	Sep 2009	EP
2141576	Jan 2010	EP
1964022	Mar 2010	EP
2184673	May 2010	EP
2390766	Nov 2011	EP
1517521	Jul 1978	GB
2319591	May 1998	GB
2327558	Jan 1999	GB
2347200	Aug 2000	GB
2351215	Dec 2000	GB
2351639	Jan 2001	GB
2373778	Oct 2002	GB
2404547	Feb 2005	GB
63-167923	Jul 1988	JP
1-142818	Jun 1989	JP
2-140822	May 1990	JP
3-271976	Dec 1991	JP
5-298002	Nov 1993	JP
6-161661	Jun 1994	JP
7-230352	Aug 1995	JP
8-76926	Mar 1996	JP
9-231004	Sep 1997	JP
10-500509	Jan 1998	JP
10-141974	May 1998	JP
11-126149	May 1999	JP
2000-501526	Feb 2000	JP
2000-137555	May 2000	JP
2000-137564	May 2000	JP
2000-163031	Jun 2000	JP
2000-163193	Jun 2000	JP
2000-163443	Jun 2000	JP
2000-163444	Jun 2000	JP
2000-222130	Aug 2000	JP
2000-322495	Nov 2000	JP
2001-290585	Oct 2001	JP
2002-254614	Sep 2002	JP
2002-342033	Nov 2002	JP
2003-296024	Oct 2003	JP
2003-330613	Nov 2003	JP
2005-056286	Mar 2005	JP
2005-082086	Mar 2005	JP
2005-234199	Sep 2005	JP
2005-234291	Sep 2005	JP
2005-242669	Sep 2005	JP
2005-322088	Nov 2005	JP
2006-102275	Apr 2006	JP
2008-508601	Mar 2008	JP
2008-146165	Jun 2008	JP
2008-312153	Dec 2008	JP
2010-503124	Jan 2010	JP
2010-503125	Jan 2010	JP
4-542637	Sep 2010	JP
2012-014299	Jan 2012	JP
10-2002-0095992	Dec 2002	KR
10-2004-0071767	Aug 2004	KR
10-2009-0057304	Jun 2009	KR
10-2009-0057421	Jun 2009	KR
WO 9429788	Dec 1994	WO
WO 9806054	Feb 1998	WO
WO 9807112	Feb 1998	WO
WO 9928812	Jun 1999	WO
WO 9940562	Aug 1999	WO
WO 9957630	Nov 1999	WO
WO 0038042	Jun 2000	WO
WO 0129702	Apr 2001	WO
WO 0177792	Oct 2001	WO
WO 0201338	Jan 2002	WO
WO 0208881	Jan 2002	WO
WO 0213176	Feb 2002	WO
WO 0221338	Mar 2002	WO
WO 03054681	Jul 2003	WO
WO 03060622	Jul 2003	WO
WO 03081458	Oct 2003	WO
WO 2004001560	Dec 2003	WO
WO 2005052773	Jun 2005	WO
WO 2006003590	Jan 2006	WO
WO 2006003591	Jan 2006	WO
WO 2006020304	Jan 2006	WO
WO 2006020305	Feb 2006	WO
WO 2006045530	May 2006	WO
WO 2006067711	Jun 2006	WO
WO 2006094308	Sep 2006	WO
WO 2006128248	Dec 2006	WO
WO 2007037806	Apr 2007	WO
WO 2007067858	Jun 2007	WO
WO 2007079425	Jul 2007	WO
WO 2007089766	Aug 2007	WO
WO 2008020446	Feb 2008	WO
WO 2008030563	Mar 2008	WO
WO 2008030779	Mar 2008	WO
WO 2008030879	Mar 2008	WO
WO 2008030880	Mar 2008	WO
WO 2008085846	Jul 2008	WO
WO 2008085848	Jul 2008	WO
WO 2008085855	Jul 2008	WO
WO 2008085871	Jul 2008	WO
WO 2008085877	Jul 2008	WO
WO 2008086218	Jul 2008	WO
WO 2008148021	Dec 2008	WO
WO 2009018314	Feb 2009	WO
WO 2009111189	Sep 2009	WO
WO 2009111458	Sep 2009	WO
WO 2009111459	Sep 2009	WO
WO 2009111480	Sep 2009	WO
WO 2011045805	Apr 2011	WO

Non-Patent Literature Citations (569)

Entry
Board Opinion received for Chinese Patent Application No. 200880001827.7, mailed on Apr. 9, 2015, 11 pages (5 pages of English Translation and 6 pages of Official Copy).
Office Action received for Korean Patent Application No. 10-2013-7000337, mailed on Apr. 28, 2014, 7 pages (3 pages of English Translation and 4 pages of Official Copy).
Apple Inc. vs. Samsung Electronics Co. Ltd., et al., 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., et al., Samsung's Motion to Supplement Invalidity Contentions, Case No. 11-cv-01846-LHK, filed Jan. 27, 2012 together with Exhibit 6, Jan. 27, 2012, 47 pages.
Apple Inc. vs. Samsung Electronics Co. Ltd., et al., Samsung's Patent Local Rule 3-3 and 3-4 Disclosures, Case No. 11-cv-01846-LHK, dated Oct. 7, 2011, together with Exhibits. G-1 through G-7 and Exhibit H. Oct. 7, 2011. 287 pages.
Corrected Notice of Commission Determination Not to Review an Initial Determination Terminating the Investigation as to Certain Asserted Patient Claims: ITC Inv. No. 337-TA-797, Jun. 22, 2012.
Flash to the Core Website, http://flashtothecore.praystation.com, 2002.
Flashloaded SlideMem Website http://flashloaded.com/flashcomponents/slidemem/, 2007.
Flashloaded SlideMenu Date, Flashloaded.com, 2007.
HTC Europe Co. Ltd and Apple Inc. Invalidity Claim dated Apr. 5. 2012, together with annexes, 12 pages.
HTC Europe Co. Ltd and Apple Inc. invalidity Claim dated Jul. 29, 2011, together with amended Particulars of Claim and amended Grounds of Invalidity, 22 pages.
Microsoft Word 2003 Screenshots, 1983-2003, 2 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.
Non-Final Office Action received for U.S. Appl. No. 12/042,067, mailed on Oct. 15, 2010; 4 pages.
Notice of Appeal in Expedited Appeal in Summary Proceedings dated Sep. 14, 2011, pp. 1-51.
Order Contruing Disputed Claim terms of U.S. Pat. Nos. 7,844,915 (DI 849): Apple Inc. v. Samsung Electronics Co, Ltd, et al., 5:11-cu-03846 (N.D.Cal).
Order Denying Motion for Summary Judgment (DI 1158): Apple Inc. v. Samsung Electronics Co. Ltd. et al., 5:11-cv-01846 (N.D. Cal).
Order No. 52: Initial Determination Granting Renewed Motion to Terminate Investigation With Respect to Certain Claims: ITC Inv. No. 337-TA-797.
Order No. 57: Construing the Terms of the Asserted Claims of the Patents at Issue: ITC Inv. No. 337-TA-797.
Order No. 58: Initial Determination Granting Motion to Terminate Investigation with Respect to Certain Claims: ITC Inv. No. 337-TA-797.
PlasmaplugsScrollBar Website, 2006.
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 Kleemarts, 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.
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.
Scroll Movie with Inertia, Flash Kit, Aug. 28, 2005, pp. 1-5.
Teleprompter-VBForums, 2003.
Office Action received for European Patent Application No. 08705471.4, mailed on Dec. 19, 2011, 6 pages.
Summons to Attend Oral Proceedings received for European Patent Application No. 08705751.9. mailed on Oct. 28, 2011, 9 pages.
Office Action received for European Patent Application No. 08712946.6, mailed on Oct. 20, 2014, 6 pages.
Office Action received for European Patent Application No. 08712946.6, mailed on Oct. 30, 2012, 20 pages.
Office Action received for European Patent Application No. 08712964,9 mailed on Jan. 20, 2015, 8 pages.
Office Action received for European Patent Application No. 08712964.9, mailed on Nov. 26, 2012, 6 pages.
Decision to Grant received for European Patent Application No. 08713567.9, mailed on Oct. 7, 2011, 1 page.
Office Action received for European Application No. 08713567.9, mailed on Dec. 29, 2009, 5 pages.
Extended European Search Report (incudes Partial European Search Report and European Search Opinion) received for European Patent Application No. 09154313.2, mailed on Apr. 21, 2009, 6 pages.
Office Action received for European Patent Application No. 09154313.2, mailed on Feb. 12, 2010, 1 page.
Summons to Attend Oral Proceedings received for European Patent Application No. 09154313.2, mailed on May 15, 2013, 30 pages.
Office Action received for European Patent Application No. 09700006.1, mailed on Oct. 15, 2010, 4 pages.
Summons to Attend Oral Proceedings received for European Patent Application No. 09700006,1. mailed on Mar. 7, 2013, 5 pages.
Office Action received for European Patent Application No. 097000017.9, mailed on Aug. 28, 2014, 8 pages.
Office Action received for European Patent Application No. 09700007.9, mailed on Mar. 9, 2012, 7 pages.
Office Action received for European Patent Application No. 09700007.9, mailed on Nov. 26, 2010, 5 pages.
Summons to Attend Oral Proceeding received for European Patent Application No. 09700007.9, mailed on Oct. 30, 2013, 5 pages.
Summons to Attend Oral Proceedings Received for European Patent Application No. 09700008.7, mailed on Mar. 27, 2013, 4 pages.
Office Action received for Taiwan Patent Application No. 100147539, mailed on Apr. 8, 2014, 12 pages.
Certificate of Grant received for Hong Kong Patent Application No. 10103983.1, mailed on Feb. 3, 2012, 5 pages.
Office Action received for Korean Patent Application No. 10-2009-7003574, mailed on Aug. 27, 2009, 1 page.
Notice of Allowance received for Korean Patent Application No. 10-2009-7007114, mailed on Apr. 26, 2013, 2 pages.
Notice of Allowance received for Korean Patent Application No. 10-2011-7024288, mailed on May 29, 2013, May 29, 2013, 2 pages.
Office Action received for Korean Patent Application No. 10-2012-7022239, mailed on Apr. 30, 2014, 5 pages.
Office Action received for Korean Patent Application No. 10-2012-7029618, mailed on Dec. 5, 2013, 4 pages.
Office Action received for Korean Patent Application No. 10-2013-7000337, mailed on Jun. 25, 2013, 7 pages.
Office Action received for Korean Patent Application No. 10-2013-7019463, mailed on Jun. 26, 2014, 6 pages.
Office Action received for European Patent Application No. 10712825.8, mailed on Jun. 19, 2013, 5 pages.
Final Office Action received for U.S. Appl. No. 11/520,709, mailed on Nov. 13, 2009, 8 pages.
Non-Final Office Action received for U.S. Appl. No. 11/620,709, mailed on Apr. 1, 2009, 8 pages.
Non-Final Office Action received for U.S. Appl. No. 11/620,709, mailed on Jun. 9, 2010, 8 pages.
Non-Final Office Action Received for U.S. Appl. No. 11/620,710, mailed on Jul. 21, 2010, 28 pages.
Final Office Action received for U.S. Appl. No. 11/620,715, mailed on Mar. 1, 2013, 15 pages.
Non-Final Office Action received for U.S. Appl. No. 11/620,715, mailed on Aug. 29, 2012, 16 pages.
Non-Final Office Action received for U.S. Appl. No. 11/620,717, mailed on Dec. 29, 2009, 8 pages.
Non-Final Office Action received for U.S. Appl. No. 11/620,717 mailed on Jul. 8, 2009, 6 pages.
Notice of Allowance received for U.S. Appl. No. 11/620,717, mailed on Jul. 20, 2010, 11 pages.
Final Office Action received for U.S. Appl. No. 11/520,720, mailed on Jun. 23, 2009, 17 pages.
Non-Final Office Action received for U.S. Appl. No. 11/620,720, mailed on Dec. 23, 2008, 18 pages.
Non-Final Office Action received for U.S. Appl. No. 11/620,720, mailed on Nov. 18, 2009, 17 pages.
Final Office Action received for U.S. Appl. No. 11/620,723, mailed on Nov. 17, 2009, 8 pages.
Non-Final Office Action received for U.S. Appl. No. 11/620,723, mailed on Apr. 1, 2009, 8 pages.
Non-Final Office Action received for U.S. Appl. No. 11/620,723, mailed on Jun. 8, 2010, Jun. 8, 2010, 8 pages.
Final Office Action received for U.S. Appl. No. 11/620,727 mailed on Mar. 12, 2012, 20 pages.
Final Office Action received for U.S. Appl. No. 11/620,727, mailed on Mar. 7, 2013, 23 pages.
Non-Final Office Action received for U.S. Appl. No. 11/620,727, mailed on Aug. 15, 2012, 19 pages.
Non-Final Office Action received for U.S. Appl. No. 11/620,727, mailed on Nov. 4, 2011, 15 pages.
Examiner's Amendment received for U S. Appl. No. 11/056,969, mailed on Oct. 29, 2008, 13 pages.
Notice of Allowance rereivaad for U.S. Appl. No. 11/956,969, mailed on Oct. 29, 2008, 6 pages.
Certificate of Grant received for Hong-Kong Patent Application No. 11110416.2, mailed on Nov. 30, 2012, 1 page.
Decision to Grant received for European Patent Application No. 11150786.9 , mailed on Jul. 26, 2012, 2 pages.
Extended European Search Report (includes Partial European Search Report and European Search Opinion) received for European Patent Application No. 11150786.9, mailed on Mar. 2, 2011, 5 pages.
Extended European Search Report (includes Partial European Search Report and European Search Opinion) received for European Patent Application No. 11150788.5, mailed on Mar. 1, 2011, 6 pages.
Office Action received for European Patent Application No. 11150788.5, mailed on May 9, 2014, 6 pages.
Extended European Search Report (includes European Search Report and European Search Opinion) received for European Patent Application No. 11152015.1, mailed on May 20, 2011, 9 pages.
Office Action received for European Patent Application No. 11152015.1, mailed on Jul. 26, 2013, 6 pages.
Extended European Search Report (includes Partial European Search Report and European Search Opinion) received for European Patent Application No. 11182954.5, mailed on Nov. 29, 2011, 6 pages.
European Search Report received for European Patent Application No. 11182959.4, mailed on Nov. 30, 2011, 7 pages.
European Search Report received for European Patent Application No. 11182962.8, mailed on Dec. 1, 2011, 8 pages.
Extended European Search Report (includes Partial European Search Report and European Search Opinion) received for European Patent Application No. 11182963.6, mailed on Dec. 1, 2011, 7 pages.
Extended European Search Report (includes Partial European Search Report and European Search Opinion) received for European Patent Application No. 11184167.2, mailed on Nov. 23, 2011, 6 pages.
Office Action received for European Patent Application No. 11184167.2, mailed on May 14, 2014, 6 pages.
Extended European Search Report (includes Partial European Search Report and European Search Opinion) received for European Patent Application No. 11184169.8, mailed on Nov. 24, 2011, 6 pages.
Office Action received for European Patent Application No. 11184169.8, mailed on May 14, 2014, 6 pages.
Extended European Search Report (includes Partial European Search Report and European Search Opinion) received for European Patent Application No. 11184170.6, mailed on Nov. 18, 2011, 6 pages.
Office Action received for European Patent Application No. 11164170.6, mailed on May 16, 2014, 5 pages.
Extended European Search Report (includes Partial European Search Report and European Search Opinion) received for European Patent Application No. 11184172.2, mailed on Nov. 2011, 6 pages.
Office Action received for European Patent Application No. 11184172.2, mailed on May 16, 2014, 5 pages.
Extended European Search Report (includes Partial European Search Report and European Search Opinion) received for European Patent Application No. 11184186.2, mailed on Dec. 7, 2011, 6 pages.
Office Action received for European Patent Application No. 11184186,2, mailed on Mar. 20, 2014, 5 pages.
Extended European Search Report (includes Partial European Search Report and European Search Opinion) received for European Patent Application No. 11184222.5, mailed on Jan. 13, 2012, 7 pages.
Office Action received for European Patent Application No. 11184222.5, mailed on Sep. 12, 2012, 4 pages.
Summons to Attend Oral Proceeding received for European Patent Application No. 11184222.5, mailed on Oct. 30, 2013, 5 pages.
Extended European Search Report (includes Partial European Search Report and European Search Opinion) received for European Patent Application No. 11184223.3, mailed on Jan. 13, 2012, 7 pages.
Office Action received for European Patent Application No. 11184223.3, mailed on Sep. 12, 2012, 4 pages.
Summons to Attend Oral Proceeding received for European Patent Application No. 11184223.3, mailed on Oct. 30, 2013, 5 pages.
Extended European Search Report (includes Partial European Search Report and European Search Opinion) received for European Patent Application No. 11184224.1, mailed on Jan. 13, 2012, 7 pages.
Office Action received for European Patent Application No. 11184224.1, mailed on Sep. 12, 2012, 4 pages.
Summons to Attend Oral Proceeding received for European Patent Application No. 11184224.1, mailed on Oct. 30, 2013, 6 pages.
Extended European Search Report (includes Partial European Search Report and European Search Opinion) received for European Patent Application No. 11184226.6, mailed on Jan. 13, 2012, 7 pages.
Office Action received for European Patent Application No. 11184226.6, mailed on Sep. 12, 2012, 5 pages.
Summons to Attend Oral Proceeding received for European Patent Application No. 11184226.6, mailed on Oct. 30, 2013, 5 pages.
Extended European Search Report (includes Partial European Search Report and European Search Opinion) received for European Patent Application No. 11184409.8, mailed on Nov. 30, 2011, 6 pages.
Office Action received for European Patent Application No. 11184409.8, mailed on May 16, 2014, 6 pages.
Office Action received for German Patent Application No. 112008000144.8, mailed on Oct. 29, 2010, 8 pages.
Office Action received for German Patent Application No. 112009000001.0, mailed on Oct. 19, 2010, 5 pages.
Office Action received for German Patent Application No. 112009000001.0, mailed on Sep. 26, 2012, 5 pages.
Office Action received for German Patent Application No. 112009000002.9, mailed on Sep. 26, 2012, 5 pages.
Office Action received for German Patent Application No. 112009000003.7, mailed on Aug. 10, 2010, 3 pages.
Office Action received for German Patent Application No. 112009000003.7, mailed on Sep. 26, 2012, 5 pages.
Office Action received for European Patent Application No. 11727371.4, mailed on Aug. 22, 2013, 6 pages.
Office Action received for European Patent Application No. 118087790, mailed on Jul. 1, 2014, 5 pages.
Final Office Action received for U.S. Appl. No. 12/042,067, mailed on Jul. 28. 2011, 13 pages.
Non-Final Office Action received for U.S. Appl. No. 12/042,067 mailed on Jan. 18, 2011, 14 pages.
Non-Final Office Action received for U.S. Appl. No. 12/042,067, mailed on Mar. 14, 2013, 15 pages.
Notice of Allowance received for U.S. Appl. No. 12/042,067, mailed on Dec. 6, 2013, 9 pages.
Notice of Allowance received for U.S. Appl. No. 12/042,067, mailed on Sep. 27, 2013, 10 pages.
Final Office Action received for U.S. Appl. No. 12/042,237, mailed on Jun. 2, 2011, 10 pages.
Non-Final Office Action received for U.S. Appl. No. 12/042,237, mailed on Dec. 30, 2010, 9 pages.
Non-Final Office Action received for U.S. Appl. No. 12/042,237, mailed on Sep. 14, 2011, 8 pages.
Notice of Allowance received for U.S. Appl. No. 12/042,237 mailed on Mar. 8, 2012, 8 pages.
Final Office Action received for U.S. Appl. No. 12/042,299, mailed on Jul. 8, 2011, 8 pages.
Non-Final Office Action received for U.S. Appl. No. 12/042,299, mailed on Jan. 4, 2011, 9 pages.
Non-Final Office Action received for U.S. Appl. No. 12/042,299, mailed on May 3, 2012, 9 pages.
Notice of Allowance received for U.S. Patent Application No. 12/042,299, mailed on Dec. 12, 2012, 8 pages.
Final Office Action received for U.S. Appl. No. 12/042,318, mailed on Sep. 15, 2011, 39 pages.
Non-Final Office Action received for U.S. Appl. No. 12/042,318, mailed on Feb. 18, 2011, 25 pages.
Notice of Allowance received for U.S. Appl. No. 12/042,318, mailed on Dec. 16, 2013, 30 pages.
Non-Final Office Action received for U.S. Appl. No. 12/207,429, mailed on Mar. 30, 2012, 9 pages.
Non-Final Office Action received for U.S. Appl. No. 12/270,805, mailed on Oct. 11, 2011, 27 pages.
Notice of Allowance received for U.S. Appl. No. 12/1270,805, mailed on May 17, 2012, 14 pages.
Non-Final Office Action received for U.S. Appl. No. 12/270,807 , mailed on Oct. 11, 2011, 26 pages.
Notice of Allowance received for U.S. Appl. No. 12/270,807, mailed on May 11, 2012, 12 pages.
Non-Final Office Action received for U.S. Appl. No. 12/270,810, mailed on Oct. 12, 2011, 12 pages.
Notice of Allowance received for U.S. Appl. No. 12/270,810, mailed on Jul. 11, 2012, 17 pages.
Non-Final Office Action received for U.S. Appl. No. 12/270,812 , mailed on May 17, 2012, 14 pages.
Non-Final Office Action received for U.S Appl. No. 12/270,812, mailed on Oct. 13, 2011, 12 pages.
Notice of Allowance received for U.S. Appl. No. 12/270,812, mailed on Sep. 19, 2012, 20 pages.
Final Office Action received for U.S. Appl. No. 12/270,815, mailed on Feb. 14, 2013, 12 pages.
Non-Final Office Action received for U.S. Appl. No. 12/270,815, mailed on May 17, 2012, 13 pages.
Non-Final Office Action received for U.S. Appl. No. 12/270,815, mailed on Oct. 11, 2011, 12 pages.
Non-Final Office Action received for U.S. Appl. No. 12/566/,660, mailed on Dec. 9, 2011, 6 pages.
Notice of Allowance received for U.S. Appl. No. 12/566,660, mailed on Jul. 26, 2012, 5 pages.
Notice of Allowance received for U.S. Appl. No. 12/566,660, mailed on May 24, 2012, pages.
Final Office Action received for U.S. Appl. No. 12/789,095, mailed on May 7, 2014, 17 pages.
Non-Final Office Action received for U.S. Appl. No. 12/789,695, mailed on Oct. 24, 2013, 14 pages.
Non-Final Office Action received for U.S. Appl. No. 12/769,695, mailed on Mar. 4, 2013, 13 pages.
Non-Final Office Action received for U.S. Appl. No. 12/869,182, mailed on Jun. 20, 2012, 6 pages.
Non-Final Office Action received for U.S. Appl. No 12/869,182, mailed on Oct. 24, 2011, 7 pages.
Notice of Allowance received for U.S. Appl. No. 12/869,182, mailed on Dec. 12, 2012, 5 pages.
Notice of Allowance received for U.S. Appl. No. 12/869,182, mailed on Feb. 23, 2012, 5 pages.
Notice of Allowance received for U.S. Appl. No. 12/892,848, mailed on May 15, 2013, May 15, 2013, 10 pages.
Final Office Action received for U.S. Appl. No. 12/892,851, mailed on Jul. 19, 2013, Jul. 19, 2013, 12 pages.
Non-Final Office Action received for U.S Appl. No. 12/892,851, mailed on Oct. 9, 2012, 11 pages.
Non-Final Office Action received or U.S. Appl. No. 12/692,851, mailed on May 22, 2014, 11 pages.
Extended European Search Report (includes Partial European Search Report and European Search Opinion) received for European Patent Application No. 12156394.4, mailed on Jun. 5, 2012, 6 pages.
Office Action received for European Patent Application No. 12156394.4, mailed on Oct. 22, 2014, 6 pages.
Extended European Search Report (includes Partial European Search Report and European Search Opinion) received for European Patent Application No. 12156395.1, mailed on Jun. 6, 2012, 6 pages.
Office Action received for European Patent Application No. 12156395.1, mailed on Jul. 9, 2012, 8 pages.
Office Action received for European Patent Application No. 12156395.1, mailed on Oct. 22, 2014, 6 pages.
Extended European Search Report (includes Partial European Search Report and European Search Opinion) received for European Patent Application No. 12188748.3, mailed on Feb. 28, 2013, 8 pages.
Office Action received for European Patent Application No. 12168748.3, mailed on Oct. 30, 2013, 5 pages.
Notice of Allowance received for U.S. Appl. No. 13/077,925 mailed on Jun. 27, 2013, 10 pages.
Notice of Allowance received for U.S. Appl. No. 13/077,927, mailed on Jun. 13, 2013, 10 pages.
Final Office Action received for U.S. Appl. No. 13/077,931, mailed on Sep. 9, 2013, 14 pages.
Non-Final Office Action received for U.S. Appl. No. 13/077,931, mailed on Jul. 17, 2014, 21 pages.
Non-Final Office Action received for U.S. Appl. No. 13/077,931, mailed on Jan. 3, 2013, 13 pages.
Notice of Allowance received for U.S. Appl. No. 13/077,931, mailed on Dec. 31, 2014, 8 pages.
Final Office Action received for U.S. Appl. No. 13/064,472, mailed on Jun. 17, 2014, 31 pages.
Final Office Action received for U.S. Appl. No. 13/084,472, mailed on Jun. 20, 2013, 20 pages.
Non Final Office Action received for U.S. Appl. No. 13/084,472, mailed on Dec. 6, 2013, 24 pages.
Non Final Office Action received for U.S. Appl. No. 13/054,472, mailed on Dec. 10, 2014, 25 pages.
Non-Final Office Action received for U.S. Appl. No. 13/084,472, mailed on Oct. 9, 2012, 14 pages.
Non-Final Office Action received for U.S. Appl. No. 13/163,624, mailed on Mar. 22, 2013, 9 pages.
Non-Final Office Action received for U.S. Appl. No. 13/163,624, mailed on Nov. 21, 2012, 9 pages.
Non-Final Office Action received for U.S. Appl. No. 13/163,624, mailed on Oct. 24, 2013, 8 pages.
Notice of Allowance received for U.S. Appl. No. 13/163,624, mailed on May 12, 2014, 5 pages.
Non- Final Office Action received for U.S. Appl. No. 13/163,626, mailed on Nov. 26, 2012, 9 pages.
Non-Final Office Action received for U.S. Appl. No. 13/163,626, mailed on Mar. 20, 2013, 8 pages.
Non-Final Office Action received for U.S. Appl. No. 13/163,826, mailed on Oct. 24, 2013, 8 pages.
Notice of Allowance received for U.S. Appl. No. 13/65,626, mailed on Mar. 31, 2014, 5 pages.
Non-Final Office Action received for U.S. Appl. No. 13/221,827, mailed on Jun. 23, 2014, 19 pages.
Notice of Allowance received for U.S. Appl. No. 13/221,830, mailed on Dec. 3, 2012, 5 pages.
Notice of Allowance received for U.S. Appl. No. 11/221,830, mailed on May 23, 2012, 8 pages.
Final Office Action received for U.S. Appl. No. 13/221,836, mailed on May 15, 2013, 22 pages.
Final Office Action received for U.S. Appl. No. 13/221,836, mailed on May 20, 2014, 36 pages.
Non-Final Office Action received for U.S. Appl. No. 13/221,836, mailed on Nov. 5, 2012, 16 pages.
Non-Final Office Action received for U.S. Appl. No. 13/221,836, mailed on Oct. 30, 2013, 31 pages.
Final Office Action received for U.S. Appl. No. 13/221,837, mailed on Feb. 14, 2013, 13 pages.
Non-Final Office Action received for U.S. Appl. No. 13/221,837, mailed on Jul. 24, 2012, 13 pages.
Examiner's Answer to Appeal Brief received for U.S. Appl. No. 13/251,121, mailed on Apr. 29, 2014, 41 pages.
Final Office Action received for U.S. Appl. No. 13/251,121 mailed on Jul. 9, 2012, 21 pages.
Final Office Action received for U.S. Appl. No. 13/251,121, mailed on Sep. 23, 2013, 24 pages.
Non-Final Office Action Received for U.S. Appl. No. 13/251,121, mailed on Jan. 10, 2012, 16 pages.
Non-Final Office Action Received for U.S. Appl. No. 13/251,121, mailed on May 1, 2013, 17 pages.
Examiner's Answer to Appeal Brief received for U.S. Appl. No. 13/251,146, mailed on May 7, 2014, 43 pages.
Final Office Action received for U.S. Appl. No. 13/251,146, mailed on Jun. 20, 2012, 14 pages.
Final Office Action received for U.S. Appl. No. 13/251,146 mailed on Oct. 2, 2013, 20 pages.
Non-Final Office Action eceived for U.S. Appl. No. 13/251,146, mailed on Apr. 11, 2013, 15 pages.
Non-Final Office Action received for U.S. Appl. No. 13/251,146, mailed on Jan. 31, 2012, 16 pages.
Examiner's Answer to Appeal Brief received for U.S. Appl. No. 13/251,150, mailed on Jun. 17, 2014, 48 pages.
Final Office Action received for U.S. Appl. No. 13/251,150, mailed on Dec. 11, 2013, 43 pages.
Final Office Action received for U.S. Appl. No. 13/251,150, mailed on Jul. 5, 2012, 27 pages.
Non-Final Office Action received for U.S. Appl. No. 13/251,150, mailed on Feb. 10, 2012, 23 pages.
Non-Final Office Action received for U.S. Appl. No. 13/251,150, mailed on Jun. 7, 2013, 34 pages.
Examiner's Answer to Appeal Brief received for U.S. Appl. No. 13/251,152, mailed on May 21, 2014, 45 pages.
Final Office Action received for U.S Appl. No. 13/251,152, mailed on Jun. 20, 2012, 24 pages.
Final Office Action received for U.S. Appl. No. 13/251,152, mailed on Oct. 18, 2013, 32 pages.
Non-Final Office Action received for U.S. Appl. No. 13/251,152, mailed on Apr. 23, 2013, 29 pages.
Non-Final Office Action received for U.S. Appl. No. 13/251,152, mailed on Jan. 20, 2012, 20 pages.
Non-Final Office Action received for U.S. Appl. No. 13/464,800, mailed on Jun. 18, 2012, 10 pages.
Notice of Allowance received for U.S. Appl. No. 13/464,800, mailed on Dec. 19, 2012, 9 pages.
Notice of Allowance received for U.S. Appl. No. 13/464,800, mailed on Nov. 13, 2012, 8 pages.
Notice of Allowance received for U.S. Appl. No. 13/620,390, mailed on Jan. 15, 2014, 10 pages.
Supplemental Notice of Allowance received for U.S. Appl. No. 13/620,390, mailed on Jan. 27, 2014, 2 pages.
Non-Final Office Action received for U.S. Appl. No. 13/670,378, mailed on Mar. 5, 2013, 28 pages.
Notice of Allowance received for U.S. Appl. No. 13/670,378 mailed on Jul. 24, 2013, 18 pages.
Non-Final Office Action received for U.S. Appl. No. 13/867,950, mailed on Jun. 26, 2013, 5 pages.
Notice of Allowance received for U.S. Appl. No. 13/867,950 mailed on Nov. 15, 2013, 7 pages.
Notice of Allowance received for U.S. Appl. No. 13/867,950, mailed on Oct. 22, 2013, 8 pages.
Non-Final Office Action received for U.S. Appl. No. 14/169,922, mailed on Sep. 24, 2014, 7 pages.
Notice of Allowance received for U.S. Appl. No. 14/189,922, mailed on Apr. 7, 2015, 6 pages.
Notice of Allowance received for Canadian Patent Application No. 2,755,443, mailed on Nov. 2, 2012, 1 page.
Office Action received for Canadian Patent Application No. 2,759,090, mailed on Nov. 4, 2013, 3 pages.
Office Action received for Canadian Patent Application No. 2,759,091, mailed on Nov. 7, 2013, 4 pages.
Notice of Allowance received for Canadian Patent Application No. 2,817,648 mailed on Apr. 10, 2014, 1 page.
Office Action received for Canadian Patent Application No. 2,817,890, mailed on Apr. 22, 2014, 3 pages.
Office Action received for Dutch Patent Application No. 200799.3, mailed Jun. 2012, 6 pages.
Office Action received for Australian Patent Application No. 20081130283, mailed on Jul. 1, 2008, 2 pages.
Office Action received for Australian Patent Application No. 2008201540, mailed on Feb. 19, 2009, 2 pages.
Office Action received for Australian Patent Application No. 2008201540, mailed on Jul. 15, 2009, 2 pages.
Office Action received for Chinese Patent Application No. 200860000019.9, mailed on Feb. 18, 2013, 23 pages.
Office Action received for Chinese Patent Application No. 200880000019.9, mailed on Jan. 5, 2012, 14 pages.
Office Action received for Chinese Patent Application No. 200880000019.9, mailed on Jul. 23, 2013, 7 pages.
Office Action received for Chinese Patent Application No. 200880000019.9 mailed on Nov. 23, 2010, 13 pages.
Office Action received for Chinese Patent Application No. 200880000019.9, mailed on Sep. 20, 2012, 22 pages.
Office Action received for Chinese Patent Application No. 200880001822.7, mailed on Jan. 29, 2012, 5 pages.
Office Action received for Chinese Patent Application No. 200680001527.7, mailed on Jan. 29, 2012, 5 pages.
Office Action received for Chinese Patent Application No. 200880001827.7 mailed Jul. 2, 2013, 7 pages.
Office Action received for Chinese Patent Application No. 2013880001827.7, mailed on Nov. 11, 2010, 6 pages.
Office Action received for Chinese Patent Application No. 200880001855.9, mailed on Jul. 29, 2014, 14 pages.
Office Action received for Chinese Patent Application No. 200880001855.9, mailed on Jun. 6, 2012.
Office Action received for Chinese Patent Application No. 200880001855.9, mailed on Mar. 7, 2013, 21 pages.
Office Action received for Chinese Patent Application No. 200880001855.9, mailed on Nov. 5, 2012, 17 pages.
Decision to Grant received for Japanese Patent No. 2009-080377, mailed on Jul. 27, 2012, Jul. 27, 2012, 4 pages.
Office Action received for Japanese Patent Application No. 2009-080377, mailed on Aug. 26, 2011.
Grant for Invention received for Chinese Patent Application No. ZL200910115596.4, mailed on Mar. 22, 2011, 3 pages.
Office Action received for Australian Patent Application No. 2009200366, mailed on Feb. 11, 2009, 2 pages.
Office Action received for Australian Patent Application No. 2009200493, mailed on Feb. 25, 2011, 3 pages.
Office Action received for Australian Patent Application No. 2009200493, mailed on Aug. 9, 2011, 2 pages.
Notice of Acceptance eceived for Australian Patent Application No. 2009208099, mailed on Nov. 24, 2011, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 2009208103, mailed on Apr. 14, 2011, 3 pages.
Office Action received for Australian Patent Application No. 2009208103, mailed on Apr. 8, 2010, 2 pages.
Decision to Grant received for Japanese Patent Application No. 2009-544996, mailed on May 20, 2011, 1 page.
Office Action received for Japanese Patent Application No. 2009-544996, mailed on Feb. 12, 2010, 1 page.
Office Action received for Japanese Patent Application No. 2009-544996, mailed on Nov. 8, 2010, 6 pages.
Notification of Grant received for Chinese Patent Application No. 200960000013.6, mailed on Nov. 6, 2013, 2 pages.
Office Action received for Chinese Patent Application No. 200960000013.6, mailed on Dec. 5, 2012, 7 pages.
Office Action received for Chinese Patent Application No. 200980000013.6, mailed on Jul. 3, 2013, 6 pages.
Office Action received for Chinese Patent Application No. 200980000013.6 mailed on Jun. 6, 2012, 6 pages.
Office Action received for Chinese Patent Application No. 200980000013.6, mailed on Oct. 26, 2011, 11 pages.
Decision to Grant received for Chinese Patent No. 200980000014.0, mailed on Nov. 27, 2012, 1 page.
Office Action received for Chinese Patent Application No. 200980000014.0, mailed on Jun. 13, 2012, 6 pages.
Office Action received for Chinese Patent Application No. 200980000014.0, mailed on Oct. 19, 2011, 15 pages.
Office Action received for Chinese Patent Application No. 200980000015.5, mailed on Feb. 22, 2012, 9 pages.
Office Action received for Chinese Patent Application No. 200980000015.5, mailed on Jul. 14, 2011, 8 pages.
Office Action received for Chinese Patent Application No. 200980000015.5, mailed on Sep. 11, 2012, 9 pages.
Decision to Grant received for Japanese Patent Application No. 2010-157302, mailed on Oct. 26, 2012, 3 pages.
Decision to Grant received Japanese Patent Application No. 2010-157303, mailed on Apr. 15, 2013, 3 pages.
Office Action received for Japanese Patent Application No. 2010-157303, mailed on Oct. 15, 2012, 4 pages.
Office Action received for Australian Patent Application No. 2010226120, issued on Oct. 17, 2012, 3 pages.
Office Action received for Japanese Patent Application No. 2010-502356 mailed on Oct. 24, 2011, 2 pages.
Office Action received for Japanese Patent Application No. 2010-502357 mailed on Jan. 16, 2012, 2 pages.
Office Action received for Japanese Patent Application No. 2010-502357, mailed on Sep. 2, 2013, 11 pages.
Decision to Grant received for Japanese Patent Application No. 2010-502358, mailed on Mar. 23, 2012.
Office Action received for Japanese Patent Application No. 2010-502358, mailed on Aug. 3, 2011.
Decision to Grant received Chinese Patent Application No. 201080020598.0, mailed on Apr. 24, 2014, 1 page.
Office Action received for Chinese Patent Application No. 201080020598.0, mailed on Oct. 31, 2013, 2 pages.
Notice of Allowance received for Chinese Patent Application No. 201110063183.8, mailed on Feb. 24, 2014, 4 pages.
Office Action received for Chinese Patent Application No. 201110063183.8, mailed on Aug. 26, 2013, 3 pages.
Office Action received for Chinese Patent Application No. 201110063183.6, mailed on Oct. 22, 2012, 8 pages.
Certificate of Examination received for Australian Patent No. 2011101154, mailed on dated May 7, 2012, 1 page.
Office Action received for Australian Patent Application No. 2011101154, mailed on Dec. 13, 2011, 4 pages.
Certificate of Examination received for Australian Patent No. 2011101155, mailed on May 8, 2012, 1 page.
Office Action received for Australian Patent Application No. 2011101155, mailed on Dec. 13, 2011, 3 pages.
Certificate of Examination received for Australian Patent No. 2011101156, mailed on May 8, 2012, 1 page.
Office Action received for Australian Patent Application No. 2011101156, mailed on Dec. 13, 2011, 3 pages.
Certificate of Examination received for Australian Patent No. 2011101157, mailed on May 8, 2012, 1 page.
Office Action received for Australian Patent Application No. 2011101157, mailed on Dec. 13, 2011, 4 pages.
Office Action received for Chinese Patent Application No. 201110148738.9, mailed on Aug. 5, 2013, 6 pages.
Office Action received for Chinese Patent Application No. 201110148738.9, mailed on Jan. 21, 2013, 17 pages.
Office Action received for Chinese Patent Application No. 201110463262.8, mailed on Apr. 30, 2014, 14 pages.
Notice of Acceptance received for Australian Patent Application No. 2011201639, mailed on Nov. 9, 2011, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 20111205170, mailed on Jul. 3, 2013, 2 pages.
Office Action received for Australian Patent Application No. 2011205170, mailed on Feb. 22, 2012, 3 pages.
Notice of Grant received for Chinese Patent Application No. 201120580018.5, mailed on Jul. 26, 2013, 2 pages.
Office Action received for Chinese Patent Application No. 201120580018.5, mailed on Apr. 22, 2013, 4 pages.
Office Action received for Chinese Patent Application No. 201120580018.5, mailed on Oct. 19, 2012, 4 pages.
Notice of Acceptance Received for Australian Patent Application No. 2011209720, mailed on May 1, 2014, 3 pages.
Office Action received for Australian Patent Application No. 2011209720, issued on Jun. 28, 2013, 4 pages.
Notice of Acceptance received for Australian Patent Application No. 2011265335, mailed on Nov. 8, 2012, 3 pages.
Office Action received for Australian Patent Application No. 2011265335, issued on Sep. 3, 2012, 2 pages.
Office Action received for Australian Patent Application No. 2011268047, mailed on Aug. 14, 2013, 2 pages.
Office Action received for Japanese Patent Application No. 2012-088747, mailed on Sep. 8, 2013, 4 pages.
Certification of Examination received for Australian Patent Application No. 2012100050, mailed on Mar. 2, 2012, 3 pages.
Office Action received for Chinese Patent Application No. 201210128911.3, mailed on Jan. 17, 2014, 6 pages.
Office Action received for Chinese Patent Application No. 201210128915.1, mailed on Mar. 18, 2014, 8 pages.
Office Action received for Chinese Patent Application No. 201210128932.5, mailed on Feb. 21, 2014, 12 pages.
Decision of Grant received for Japanese Patent Application No. 2012-106775, mailed on Nov. 1, 2013, 3 pages.
Office Action received for Australian Patent Application No. 2012200689, mailed on Sep. 9, 2013, 3 pages.
Office Action received for Japanese Patent Application No. 2012-218235, mailed on Sep. 24, 2013, 6 pages.
Notice of Allowance received for Japanese Patent Application No. 2012-500844, mailed on Aug. 1, 2014, 3 pages.
Office Action received for Japanese Patent Application No. 2012-500844, mailed on Feb. 24, 2014, 8 pages.
Office Action received for Japanese Patent Application No. 2012-500844, mailed on Jun. 3, 2013, 5 pages.
Notice of Allowance received for Japanese Patent Application No. 2013-515382, mailed on Aug. 22, 2014, 3 pages.
Office Action received apanese Patent Application No. 2013-515382, mailed on Nov. 18, 2013, 2 pages.
Certificate of Grant received for Turkish part of European Patent Application No. 2126678, mailed on Jun. 21, 2012, 2 pages.
Notice of Allowance received for Canadian Patent Application No. 2,858,177, mailed on Jan. 30, 2012, 1 page.
Office Action received for Canadian Patent Application No. 2,658,177, mailed on Dec. 1, 2009, 2 pages.
Office Action received for Canadian Patent Application No. 2,658,177, mailed on Jun. 22, 2011, 2 pages.
Ex-parte Reexamination Final Communication received for U.S. Appl. No. 90/012,332, mailed on Jul. 26, 2013, Jul. 26, 2013, 61 pages.
Ex-parte Reexamination Non-Final Communication received for U.S. Appl. No. 90/012,332, mailed on Dec. 19, 2012, 38 pages.
Agarawala et al., “Keepin' It Real: Pushing the Desktop Metaphor with Physics, Piles and the Pen”, CHI 2006, Montreal, Canada, Apr. 22-27, 2006, pp. 1283-1292.
Allen, Jay, “Override the GNU C Library—Painlessly”, available at <http//www.ibm.com/developerworks/linux/library/l-glibc/index.html>, Apr. 1, 2002, 4 pages.
Anonymous. “FireGestures Version History: Add-ons for Firefox”, Internet Article, available at <http://addons.mozilla.org/en-US/firefox/addons/version/3366>, retrieved on Oct. 28, 2009, 6 pages.
Anonymous, “Firegestures: Changelog”, Internet Article, available at <http://www.xuldev.org/firegestures/changelog.php>, retrieved on Oct. 27, 2009, 8 pages.
Anonymous, “Firegestures: Firefox Extension”, Internet Article, available at http://www.xuldev.org/firegestures/>, retrieved on Oct. 27, 2009, 2 pages.
Apple Inc., “SafariWeb Content Guide for iPhone”, Feb. 5, 2005, 96 pages.
Balakrishnan et al., “Performance Differences in teh Fingers, Wrist, and Forearm in Computer Input Control”, ACM Conference on Human Factors in Computing Systems (CHI '97), 1997, pp. 303-310.
Ballard, Paul, “Microsoft Makes Research Technologies Available for Licensing”, available at http://www.theserveside.com/discussions/thread.tss?thread—id=33761>, May 5, 2005, 8 pages.
Bartlett et al., “Rock ‘n’ Scroll is here to stay [user interface]”, Computer Graphics and Applications. IEEE, vol. 20, Issue 3, May/Jun. 2000.
Bederson et al., “Jazz: An Extensible 2D+Zooming Graphics Toolkit in Java”, Jul. 1999.
Bederson et al., “Jazz: An Extensible Zoomable User Interface Graphics Toolkit in Java”, ACM Symposium on User Interfaces Software and Technology, May 2000.
Bederson et al. “Pad++: A Zooming Graphical Interface for Exploring Alternate Interface Physics”, UIST' 94 Proceedings of the 7th Annual ACM symposium on User Interface Software and Technology, Nov. 1994, pp. 17-26.
Bederson et al., “PhotoMesa 3.1.2 ScreenShots”, 2004-2006, 5 pages.
Benko et al., “Precise Selection Techniques for Multi-Touch Screens”, CHI 2006, Apr. 22-27, 2006, 10 pages.
Bier et al., “Snap-Dragging”, Proceedings of SIGGRAPH 86, Computer Graphics (20) 4, 1986, pp. 233-240.
Brown et al., “Distributed Active Objects”, Computer Networks and ISDN Systems, vol. 28, No. 11, May 1996, pp. 1037-1052.
Browne et al., “Designing a Collaborative Finger Painting Application for Children”, UM Computer Science Department, CS-TR-4184, 2000.
Buxton. W.. “Invited Paper: A Touching Story: A Personal Perspective on the Histsory of Touch Interfaces Past and Future”, Society for Information Display (SID) Symposium Digest of Technical Papers, vol. 41(1), Session 31, May 2010, pp. 444-448.
Buxton. “Lexical and Pragmatic Considerations of Input Structures”, Computer Graphics, vol. 17, No. 1, 1983, pp. 31-37.
Buxton, Bill, “Multi-Touch Systems that I Have Known and Loved”, available at <http://www.billbuxton.com/multitouchOverview.html>, Jan. 12, 2007, 14 pages.
C.A.R. Hoare, “Programming Techniques—Communicating Sequential Processes”, Communications of the ACM, vol. 21, No. 8, Aug. 1978, pp. 666-677.
Cao et al., “Interacting with Dynamically Defined Information Spaces using a Handheld Projector and a Pen”, UIST '06, Montreux, Switzerland, Oct. 15-16, 2006, pp. 225-234.
Captain, Sean, “Future Gear: Keyless (Data) Entry”, PCWorld, Apr. 24, 2002.
Chang et al., “Animation: From Cartoons to the User Interface”, UIST '93 Proceedings of the 6th Annual ACM Symposium on User Interface Software and Technology, Nov. 1993, pp. 45-55.
Chartier, David, “Apple Releases iOS 4.3 beta for Developers”, available at <http://www.macworld.com/article/1157114/ios—4—3.html>, Jan. 12, 2011, 7 pages.
Chen, Tom, “The Web is Everywhere”, IEEE Communications Magazine, Sep. 2007, p. 16.
Cheng et al., “Navigation Control and Gesture Recognition Input Device for Small, Portable User Interfaces”. Synaptics, Inc. of San Jose, California, Jun. 11, 2004, pp. 1-13.
Dannenberg et al., “A Gesture Based User Interface Prototyping System”, UIST '89 Proceedings of the 2nd Annual ACM Siggraph symposium on User interface software and technology, 1989, pp. 127-132.
Davidson et al., “Synthesis and Control on Large Scale Multi-Touch Sensing Displays” In Proceedings of the 2006 Conference on New Interfaces for Musical Expression, 2006, pp. 218-219.
Davis, Joshua, “Flash to the Core—An lnteractive Sketchbook”, available at <http://flashtothecore.praystation.com/menu.html>, 2002, 3 pages.
Davis, “Lateral Histograms for Efficient Object Location: Speed Versus Ambiguity”, Pattern Recognition Letters, vol. 6(3) Aug. 1987, pp. 189-198.
Dewid. R D., “Scroll Control Box”. IBM Technical Disclosure Bulletin, vol. 38, No. 4, Apr. 1993, pp. 399-403.
Dietz et al., “Diamondtouch: A Multi-User Touch Technology”, Mitsubishi Electric Research Laboratories. Oct. 2003, 11 pages.
Dietz et al., “DT Controls: Adding Identity to Physical interfaces”, UIST '05, Seattle, Washington, USA, Oct. 23-27, 2005.
Dietz et al., “Submerging Technologies”, ACM SIGGRAPH 2006 Sketches, 2006.
Dodge et al., “Microsoft Office Excel 2003 Office Manual”, Microsoft Press, vol. 1, Unable to Locate English Translation, Jul. 12, 2004, 5 pages.
Duce et al., “An Approach to Hierarchical Input Device”, Computer Graphics Forum, vol. 9(1),1990, pp. 1-16.
Duce et al., “Components, Frameworks and GKS Input”, CWI Report, No. CS-R8947: Amsterdam, CWI, 1980, pp. 87-106.
Epps et al., “A Study of Hand Shape Use in Tabletop Gesture Interaction”, CHI 2006—Work-in-progress, Montreal, Quebec, Canada, Jul. 22-27, 2006, pp. 748-753.
Erickson, T.D, “Working with Interface Metaphors, in Human-computer Itneraction”, 1995, pp. 65-73.
Esenther et al., “DiamondTouch SDK: Support for Multi-user, Multi-Touch Applications”, Mistsubishi Electric Research Laboratories, Nov. 2002, 5 pages.
Esenther et al., “Fluid DTMouse: Better Mouse Support for Touch-Based Interactions”, AVI'06, Venezia, Italy, May 23-26, 2006.
Esenther et al., “Multi-User Multi-Touch Games on Diamond Touch with the DTFlash Toolkit”, Dec. 2005, 5 pages.
Esenther et al., “RemoteDT: Support for Multi-Site Table Collaboration”, International Conference on Collaboration Technologies (CollabTech) Jul. 2006.
Everitt et al., “Modal Spaces: Spatial Multiplexing to Mediate Direct-Touch Input on Large Displays”, CHI 2005, Portland, Oregon, USA, Apr. 2-7, 2005, pp. 1359-1362.
Everitt et al., “MultiSpace: Enabling Electronic Document Micro-mobility in Table-Centric, Multi Device Environments”, First IEEE International Workshop on Horizontal Interactive Human-Computer Systems, TableTop 2006, 2006.
Everitt et al., “Observations of a Shared Tabletop User Study”, CSCW '04, Chicago, USA, Nov. 6-10, 2004.
Everitt, Katherine E., “UbiTable: Impromptu Face-to-Face Collaboration on Horizontal Interactive Surfaces”, Mitsubishi Electric Research Laboratories, Sep. 2003, 10 pages.
Faconti et al., “The Input Model of Standard Graphics Systems Revisited by Formal Specification”. Eurographics '92. vol. 11, No. 3, 1992, pp. C-237 to C-251.
Fearing, R S., “Tactile Sensing Mechanisms”, The International Journal of Robotics Research, vol. 9, No. 3, Jun. 1990, pp. 3-23.
Ferg, “Event-Driven Programming: Introduction, Tutorial, History”, Version 0.2, Feb. 8, 2006, pp. 1-59.
Fingerworks Inc., “FingerWork Installation and Operation Guide for the TouchStream ST & TouchStream LP”, 2002, pp. 1-25.
Fitzmaurice et al., “Bricks: Laying the Foundations for Graspable User Interfaces”, Proceeding of the ACM Conference on Human Factors in Computing Systems (CHI '95), New York: ACM, 1995, pp. 1-8.
Flanagan, David, “javaScript”, 5th Edition, O'reilly Japan, Jan. 31, 2008, pp. 405-437 (Japanese Language).
Foley et al., “The Art of Natural Graphic Man—Machine Conversation”, Proceedings of the IEEE, vol. 62, No. 4, Apr. 1974, pp. 462-471.
Forlines at al., “DTLens: Multi-user Tabletop Spatial Data Exploration”. UIST'05, Oct. 23-27, 2005, 6 pages.
Forlines et al., “Exploring the Effects of Group Size and Display Configuration on Visual Search”, CSCW '06, Banff, Alberta, Canada, Nov. 4-8, 2006, pp. 11-20.
Forlines et al., “Glimpse: A Novel Input Model for Multi-Level Devices”, CHI'2005, Apr. 2-7, 2005, 6 pages.
Forlines et al., “HybridPointing Fluid Switching Between Absolute and Relative Pointing with a Direct Input Device”, UIST '06, Montreaux, Switzerland, Oct. 15-18, 2006, pp. 211-220.
Forlines et al., “Multi-User, Multi-Display Interaction with a Single-User, Single-Display Geospatial Application”, Mitsubishi Electric Research Laboratories, Inc., TR2006-083, Oct. 2006, pp. -797HTC-0043238-797HTC-0043242.
Forlines et al., “Under My Finger: Human Factors in Pushing and Rotating Documents Across the Table”, Proceedings of Human-Computer Interaction—Interact 2005: IFIP TC13 Interaction Conference, Rome Italy, Dec. 2005, pp. 994-997.
Forlines et al., “Zoom-and-Pick: Facilitating Visual Zooming and Precision Pointing with Interactive Handheld Projectors”, UIST '05, Seattle, Washington, USA, Oct. 23-27, 2005, pp. 73-82.
Fukuchi, Kentaro, “Concurrent Manipulation of Multiple Components on Graphical User Interface”, PhD Thesis, Tokyo Institute of Technology, Oct. 23, 2006, 160 pages.
Fukuchi et al., “Interaction Techniques for SmartSkin”, In Proceedings of UIST '02, 2002, 2 pages.
Fukuchi et al., “Marble Market: Bimanual Interactive Game with a Body Shape Sensor”, 2007.
Fukuchi, “Multi-track Scratch Player on a Multi-Touch Sensing Device”, 2007.
Fukuchi et al., “SmartSkin”, 2003.
Furuichi et al., “DTMap Demo: Interactive Tabletop Maps for Ubiquitous computing”, UbiComp 2005.
Gingold et al., “A Direct Texture Placers ent and Editing Interface”, UIST '06, Montreux, Switz, Oct. 15-18, 2006, pp. 23-31.
Gleicher, M., “Image Snapping”, 1995, pp. 183-190.
Gross, Mark D., “Grids in Design and CAD”, Proceedings of Association for Computer Aided Design in Architecture. 1991, pp. 1-11.
Grossman at at. “Multi-Finger Gestural Interaction with 3D Volumetric Displays”, UIST '04, Santa Fe, New Mexico, USA, Oct. 24-27, 2004.
Grossman at al., “The Design and Evaluation of Selection Techniques for 3D Volumetric Displays”, UIST '06, Montreux, Switzerland Oct. 15-18, 2006, pp. 3-12.
Han, Jeff, “Jeff Han Demos his Breakthrough Touchscreen”, TED, Ideas Spreading, available at <http://www.ted.com/tals//jeff—han—demos—his—breakthrough—touchscreen.html>, Feb. 25, 2006, 12 pages.
Han, Jefferson Y., “Low-Cost Multi-Touch Sensing Through Frustrated Total Internal Reflection”, Oct. 23, 2005, pp. 115-118.
Han et al., “Measuring Bidirectional Texture Reflectance with a Kaleidoscope”, 2003, pp. 741-748.
Han, “Media Mirror”.
Han, Jeff Y., “Multi-Touch Interaction Research”, available at <http://mrl.nyu.edu/˜jhan/ftirtouch/>, retrieved on Apr. 13, 2006, 4 pages.
Han, “Multi-touch Interaction Wall”, In ACM SIGGRAPH, 2006, 1 page.
Han. “Multi-Touch Sensing Through Frustrated Total Internal Reflection”, 2 pages.
Han, “Unveiling the Genius of Multi-Touch Interface Design”, Feb. 2006.
Hancock et al., “Exploring Non-Speech Auditory Feedback at an Interactive Multi-User Tabletop”, GI '05 Proceedings of Graphics Interface, 2005.
Hansen et al., “Events Not Equal to GUIs”, SIGCSE '04, Norfolk, Virginia, USA, Mar. 3-7, 2004, pp. 378-381.
Harrison et al., “Squeeze Me, Hold Me, Tilt Me! An Exploration of Manipulative User Interfaces”, CHI '98, Los Angelse, CA USA, Apr. 1998, pp. 17-24.
Hauptman et al., “Gesture Analysis for Graphic Manipulation”, Nov. 28, 1988, pp. 1-15.
Holzner, “Built-in JavaScript Objects”, JavaScript Program Control Objects, 1998, pp. 71-79.
IBM, “Method to Disable and Enable a Touch Pad Pointing Device or Tablet Input Device Using Gestures”, Jun. 11, 2002, pp. 1-3.
Ishak et al., “Content-Aware Scrolling”, UIST'06 Proceedings of the 19th annual ACM symposium on User Interface Software and Technology, Montrex, Switzerland, Oct. 15-18, 2006.
Jazzmutant, “Lemur v1.3 Documentation/Addendum”, available at <http://www.jazzmutant.com/support—download.php>, Mar. 22, 2005, 3 pages.
Jazzmutant, “Lemur v1.3 Examples Package: CursorModes.xml”, available at <http://www.jazzmutant.com/support—download.php>, Jan. 31, 2006, 4 pages.
Jazzmutant “Lemur v1.3 Examples Package: LightStepSeq.xml”, available at <http://www.jazzmutant.com/support—download.php>, Jan. 31, 2006, 5 pages.
Jazzmutant, “Support”, available at http://web.archive.org/web/20060421144624/http://www.jazzmutant.com/support—download.php>, Apr. 21, 2006, 2 pages.
Jazzmutant, “The Lemur Owner's Manual”, available at <http://www.jazzmutant.com/support—download.php>, Oct. 31, 2005, 108 pages.
Johnson, Jeff A., “A Comparison of User Interfaces for Panning on a Touch-Controlled Display”, CHI '95 Proceedings, Mosaic of Creativity, May 7-11, 1995, pp. 218-225.
Johnson et al., “The Effect of Touch-Pad Size on Pointing Accuracy”, Apr. 1994, pp. 1-8.
Justice Floyd, “UK Royal Court of Justice: (2012) EWHC 1789 (Pat)—Extracts”, available at <http://www.judiciary.gov.uk/Resources/JCO/Documents/Judgments/htc-v-apple-judgment.pdf>, Jul. 4, 2012, 26 pages.
Karlson et al., “AppLens and LaunchTile: Two Designs for One-Handed Thumb Use on Small Devices”, Powerpoint Presentation, CHI 2005, 17 pages.
Karlson et al., “AppLens and LaunchTile: Two Designs for One-Handed Thumb Use on Small Devices”, CHI 2005, Papers: Small Devices 1, Apr. 2-7, 2005, pp. 201-210.
Kenny, “UIGestureRecognizer”, available at <http://iphonedevwiki.net/index.php?title=UIGestureRecognizer&oldid=-319>, Oct. 31, 2009, 3 pages.
Kim et al., “HCI (Human Computer Interaction) Using Multi-touch Tabletop Display”, IEEE Pacific Rim Conference on Communications, Computers and Signal Processing, Victoria, BC, Canada, pp. 391-394.
Kim et al., “Multi-touch Interaction for Table-Top Display”, ICAT 2006, LNCS 4282, pp. 1273-1282.
Kirk, “Optimal Control Theory—An introduction, Numerical Determination of Optimal Trajectories”, 1970, pp. 331-343.
Krolik, M., “RV Creator 3.41”, Cross Browser DHTML 360 Panorama Image Viewer (PIV), 1999.
Kurtenbach et al., “The Design of A GUI Paradigm Based on Tablets, Two-Hands, and Transparency”, Mar. 27, 1997, 8 pages.
Laurel, B., “The Art of Human-Computer Interface Design”, 1990, pp. 65-73.
Lee et al., “Haptic Pen: Tactile Feedback Stylus for Touch Screens”. Mitsubishi Electric Research Laboratories, Oct. 2004, 6 pages.
Lytle, “FingerWorks Announces a Gesture Keyboard for Apple PowerBooks”, PR Newswire.
Malik, “An Exploration of Multi-Finger Interaction on Multi-Touch Surfaces”, Doctoral Dissertation, 2007, pp. 1-169.
Malik et al., “Interactinng with Large Displays from a Distance with Vision-Tracked Multi-Finger Gestural Input”, UIST '05, Seattle, Washington, USA, 2005, pp. 43-52.
Malik et al., “Visual Touchpad: A Two-Handed Gestural Input Device”, ICMI'04 Proceedings of the 6th International Conference an Multimodal Intercases, ACM, Oct. 13-15, 2004, pp. 289-296.
Masui et al., “Elastic Graphical Interfaces for Precise Data Manipulation”, ACM Conference on Human Factors in Computing Systems (CHI '95), Conference Companion, Apr. 1995, pp. 143-144.
Mertz et al., “The Influence of Design Techniques on User Interfaces: The DigiStrips Experiment for Air Traffic Control”, Proceeding of HCI-Aero 2000 International Conference on Human-Computer Interaction in Aeronautics, 2000, 6 pages.
Microsoft, “Microsoft® Windows® Software Development Kit—Update for Windows Vista.TM ”, available at <http://www.microsoft.com/download/en/details.aspx?displaying=en&id=423719> Mar. 22, 2007, 26 pages.
Microsoft, “Window Styles—Microsoft Windows SDK”, Screenshot, Mar. 22, 2007, 2 pages.
Miller, Dana, “PersonalJava Application Environment”, available at <http://java.sun.com/products/personaljava/touchable/>, Jun. 8, 1999, 12 pages.
Millhollon et al., “Microsoft Office Word 2003 inside Out”, 2004, 7 pages.
Minsky, “Manipulating Simulated Objects with Real-World Gestures Using a Force and Position Sensitive Screen”, Proceedings of the 11th Annual Conference on Computer Graphics and Interactive Techniques, Jul. 1984, pp. 195-203.
Moghaddam et al., “Visualization & User-Modeling for Browsing Personal Photo Libraries”, International Journal of Computer Vision vol. 56, No. 1/2, 2004, pp. 109-130.
Morris et al., “Beyond Social Protocols: Multi-User Coordination Policies for Co-located Groupware”, CSCW '04, Chicago, Illinois, USA, Nov. 6-10, 2004.
Morris et al., “Conflict Resolution in Paper and Digital Worlds: Two Surveys of User Expectations”, ACM Conference on Computer Supported Cooperative Work (CSCW), Chicago, Illinois.
Moscovich et al., “A Multifinger Interface for Performance Animation of Deformable Drawings”, UIST '05—Adjunct Proceedings of the 18th Annual ACM Symposium on User Interface Software and Technology, 2005.
Moscovich et al., “Multi-Finger Cursor Techniques”, GI '06 Proceedings of Graphics Interface 2006, Quebec City, Quebec, Canada, Jun. 9, 2006, 7 pages.
Moyle et al., “The Design and Evaluation of a Rick Gesture for ‘Back’ and ‘Forward’ in Web Browsers”AUIC '03 Proceedings of the Fourth Australasian user interface conference on User interfaces 2003, vol. 18.
Myers et al., “Past, Present, and Future of User Interface Software Tools”, ACM Transactions on Computer-Human interaction, vol. 7, No. 1, Mar. 2000, pp. 3-28.
Nairn, Rown, “Breakthrough Internet Device”, Eureka Man, available at <URL:https://web.archive.org web/20070709083826/http:/eurekaman.com/towards-multi-touch-in-the-browser>, retrieved on Jul. 9, 2007, 2 pages.
Nakatani et al., “Soft Machines: A Philosophy of User-Computer Interface Design”, CHI '83, Proceedings. Dec. 1983, pp. 19-23.
Narayanaswamy et al., “User interface for a PCS Smart Phone”, Multimedia Computing and Systems, IEEE Conference 1999, Published, Jun. 7-11, 1999, vol. 1, pp. 777-781.
Newman; “A System for Interactive Graphical Programming”. AFIPS '68 (Spring) Proceedings of the Apr. 30-May 2, 1988, spring joint computer conference, pp. 47-54.
Ogawa et al., “Preprocessing for Chinese Character Recognition and Global Classification of Handwritten Chinese Characters”, Pattern Recognition, vol. 11, 1979, pp. 1-7.
Owen, G S., “Principles of Animation: Slow In and Out”, Mar. 13, 1999.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2005/000089, issued on Jun. 18, 2005, 5 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2005/000089, mailed on May 31, 2005, 7 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2008/000058, mailed on Jul. 7, 2009, 5 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2008/000058, mailed on Jul. 31, 2008, 10 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2008/000060, mailed on Jul. 7, 2009, 7 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2008/000060, mailed on Apr. 22, 2008, 12 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2008/000069, mailed on Jul. 7, 2009, 8 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2008/000069, mailed on May 2, 2008, 16 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2008/000089, mailed on Jul. 7, 2009, 9 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2008/000089, mailed on Jun. 4, 2008, 14 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2008/000103, mailed on Jul. 7, 2009, 9 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2008/000103, mailed on Jun. 3, 2008, 11 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2008/050292, mailed on Sep. 19, 2008, 19 pages.
Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2008/050292, mailed on Jul. 18, 2008, 4 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2009/034772, mailed on Sep. 16, 2010, 8 pages.
International Search Report received for PCT Patent Application No. PCT/US2009/034772, mailed on Apr. 16, 2009, 3 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2009/035856, mailed on Sep. 16, 2010, 8 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2009/065868, mailed on Jul. 3, 2009, 7 pages.
International Report on Patentability received for PCT Patent Application No. PCT/US2009/035858, mailed on Sep. 16, 2010, 7 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2009/035858, mailed on Jul. 3, 2009, 10 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2009/035874, mailed on Sep. 16, 2010, 3 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2009/035874, mailed on Nov. 11, 2009, 7 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2010/027118, mailed on Sep. 20, 2011, 10 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2010/027118, mailed on Oct. 5, 2010, 14 pages.
Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2010/027118, mailed on Jul. 13, 2010, 7 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2011/022516, mailed on Aug. 9, 2012, 11 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2011/022516, mailed on May 20, 2011, 16 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2011/039588, mailed on Dec. 27, 2012, 10 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2011/039583 mailed on Dec. 13, 2011, 12 pages.
International Preliminary report on Patentability received for PCT Patent Application No. PCT/US2011/065859, mailed on Jul. 4, 2013, 16 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2011/065859, mailed on Jun. 1, 2012, 22 pages.
Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2011/065859, mailed on Mar. 12, 2012, 10 pages.
Petzold, Charles, “Programming Microsoft Windows with C#”, Jan. 18. 2002, 5 pages.
Pickering, J. A., “Touch-Sensitive Screens: The Technologies and Their Application”, International Journal of Man-Machine Studies, vol. 25, No. 3, Sep. 1986, pp. 249-269.
Pixley, Tom (Editor)., “Document Object Model (DOM) Level 2 Events Specifications (Version 1.0)”, W3C Recommendation, Nov. 13, 2000, 47 pages.
Plaisant, C., “Touchscreen Toggle Design”, Available at <http://www.youtube.com/watch?v=wFWbdxicvK0>, 1991.
Plaisant et al., “Touchscreen Toggle Design”, CHI'92, May 3-7, 1992, pp. 687-668.
Pogue, David, “Windows Vista for Starters: The Missing Manual”, available at <http://academic.safarobooksonline.com/book/operating-systems/0596528254>, Jan. 25, 2007, 18 pages.
Raab, “Pedagogical Power Tools for Teaching Java” ITiCSE 2000 Jul. 2000 Helsinki, Finland, pp. 156-159.
Raiha, Liisa, “Delegation: Dynamic Specialization”, ACM, 1994, pp. 172-179.
Rasala, “Java Power Tools: Model Software for Teaching Object-Oriented Design”, SIGCSE 2001 Feb. 2001 Charlotte, NC USA, pp. 297-301.
Raskar et al., “Intelligent Clusters and Collaborative Projector-based Displays”, NSF Lake Tahoe Workshop on Collaborative Virtual Reality and Visualization, Oct. 2003, pp. 1-5.
Rekimoto et al., “Augmented Surfaces: A Spatially Continuous Work Space for Hybrid Computing Environments”, CHI '99 Proceedings of the SIGCHI Conference on Human Factors in Computing Systems: the CHI is the Limit, 1999.
Rekimoto, “Pick-and-Drop: A Direct Manipulation Technique for Multiple Computer Environments”, UIST '97 Proceedings of the 10th Annual ACM Symposium on User Interface Software and Technology, Banff, Alberta, Canada, 1997, pp. 31-39.
Rekimoto, “SmartSkin: An Infrastructre for Freehand Manipulation on Interactive Surfaces”, Apr. 2002.
Robertson et al., “Data Mountain: Using Spatial Memory for Document Management”, UIST '98: Proceedings of the 11th Annual ACM symposium on User Interface Software and Technology, San Francisco, 1998, pp. 153-162.
Rogers, Michael, “It's for You! An iPhone Development Primer for the Busy College Professor”, Journal of Computing Sciences in Colleges, vol. 25, No. 1, Oct. 2009, pp. 94-101.
Rosenberg et al., “Real-Time Stereo Vision Using Semi-Global Matching on Programmable Graphics Hardware”, ACM SIGGRAPH 2006 Sketches, 2006.
Rosenthal et al., “The Detailed Semantics of Graphics Input Devices”, Computer Graphics, vol. 16, No. 3, Jul. 1982, pp. 33-38.
Rubine, Dean, “Combining Gestures and Direct Manipulation”, CHI '92, May 3-7, 1992, pp. 659-660.
Rubine, “Intergrating Gesture Recognition and Direct Manipulation”, Usenix Technical Conference, 1991, pp. 1-18.
Rubine et al., “Programmable Finger-Tracing lnstrument Controllers”, Computer Music Journal, vol. 14, No. 1 New Performance Interfaces, Spring 1990, pp. 26-41.
Rubine, D., “Specifying Gestures by Example”, Computer Graphics vol. 25, No. 4, Jul. 1991, 329-337.
Rubine, Dean Harris., “The Automatic Recognition of Gestures”, CMU-CS-91-202, Thesis Submitted in Partial Fulfillment of the Requirements for the Degree of Doctor of Philosophy in Computer Science at Carnegie Mellon University, Dec. 1991, 285 pages.
Rubine et al., “The VideoHarp”, ICMC Proceedings, 1988, pp. 49-55.
Ryall et al., “Experiences with and Observations of Direct-Touch Tabletops”, Tabletop '06 Proceedings of the First IEEE International Workshop on Horizontal Interactive Human-Computer Systems.
Ryall et al., “Exploring the Effects of Group Size and Table Size on Interactions with Tabletop Shared-Display Groupware”, CSCW, '04, Chicago, Illinois, USA, Nov. 6-10, 2004.
Ryall et al., “iDwidgets: Parameterizing Widgets by User Identity”, Interact 2005 (Tenth IFIP TC13 Int Conf on Human-Computer Interaction).
Ryall et al., “Temporal Magic Lens: Combined Spatial and Temporal Query and Presentation”, Interact 2005 (Tenth IFIP TC13 Int. Conf on Human-Computer Interaction), 2005.
Salmoni, “The Zooming User Interface”, Advogato, available at <http://www.advogato.org/articie/788.html>, Aug. 16, 2004, 14 pages.
Sears et al., “High Precision Touchscreens: Design Strategies and Comparisons with a Mouse”, International Journal of Man-Machine Studies, vol. 34, No. 4, Apr. 1991, pp. 593-613.
Sensor Fram Corporation, “The Sensor Frame Graphic Manipulator NASA Phase II Final Report”, May 8, 1990, pp. 1-25.
Seonkyoo Lee, “A Fast Multiple-Touch-Sensitive Input Device” Oct. 1984.
Sharon, “Haptic Perception with an Articulated Sensate Robot Hand”, Robotica, vol. 10, 1992, pp. 497-508.
Shen et al.. “Building and Sharing Digital Group Histories”, CSCW '02, New Orleans, Louisiana, USA, Nov. 16-20, 2002.
Shen et al., “CoR2Ds: Context-Rooted Rotatable Draggabies for Tabletop Interaction”. CHI 2005, Portland, Oregon, USA, Apr. 2-7, 2005, pp. 1781-1784.
Shen et al., “DiamondSpin: An Extensible Toolkit for Around-the-Table Interaction”, Apr. 24-29, 2004, 8 pages.
Shen et al., “Multi-User Interface and interactions on Direct-Touch Horizontal Surfaces: Collaborative Tabletop Research at MERL”, First IEEE International Workshop on Horizontal Interactive Human-Computer Systems, TableTop 2006, 2006.
Shen et al., “Personal Digital Historian, Story Sharing Around the Table”, Interactions—Winds of Change, vol. 10, No. 2, 2003, pp. 15-22.
Shen et al., “Three Modes of Multi-Surface Interaction and Visualization”, ACM CHI '06 International Conference, Montreal, Canada, Apr. 22-23, 2006, pp. 1-4.
Shneiderman, “Future Directions for Human—Computer Interaction”. International Journal of Human Computer Interaction, 1990, pp. 1-19.
Sibert et al., “An Object-Oriented User Interface Management System”, SIGGRAPH '86, vol. 20, No. 4, 1986, pp. 259-268.
Siegel et al., “Performance ANalysis of a Tactile Sensor”, IEEE international Conference on Robotics and Automation, Proceedings, 1987, pp. 1493-1499.
Smith et al., “The Radial Scroll Tool: Scrolling Support for Stylus- or Touch-Based Document Navigation”, UIST '04 Proceedings of the 17th Annual ACM symposium on User Interface Software and Technology, Santa Fe, New Mexico, Oct. 24-27, 2004, pp. 1-4.
Son et al., “Comparison of Contact Sensor Localization Abilities During Manipulation”, Robotics and Autonomous Systems, vol. 17(4), 1996, pp. 217-233.
Sony, “The Power of a Full-Sized PC in the Palm of our Hand”, 2004.
Stauffer, “Progress in Tactile Sensor Development”, Robotics Today, 1983, pp. 43-49.
Stein, “What We Swept Under the Rug: Radicaly Rethinking CSI”, Computer Science Education, vol. 8, No. 2, 1998, pp. 118-129.
Sugimoto et al., “Hybridtouch: An Intuitive Manipulation Technique for PDAs Using Their Front and Rear Surfaces”, MobileHCI '06, Helsinki, Finland, Sep. 12-15, 2006, pp. 137-140.
Sugiyama et al., “Tactile Image Detection Using a 1k-element Silicon Pressure Sensor Array”, Sensors and Actuators, A21-A23, 1990, pp. 397-400.
Sun et al., “Flipper: A New Method of Digital Document Navigation”, CHI '05 extended abstracts on Human factors in computing systems, Portland, Oregon, Apr. 2-7, 2005, pp. 2001-2004.
TE Connectivity, “CarrollTouch infrared Touch Technology”.
Thomas et al., “Animating Direct Manipulation Interfaces”, UIST 95 Pittsburg. PA, Nov. 1995, pp. 3-12.
Thomas et al., “Applying Cartoon Animation Techniques to Graphical User Interfaces”, ACM Transactions on Computer-Human Interaction, vol. 8, No. 3, Sep. 2001, pp. 198-222.
Tidwell, Jenifer, “Magnetism”, Designing Interfaces, Section 85, 2006, pp. 261-262.
Tse et al., “Enabling Interaction with Single User Applications Through Speech and Gestures on a Multi-User Tabletop”, Mitsubishi Electric Research Laboratories, 2005, pp. 336-343.
Tse et al., “GSI Demo: Multiuser Gesture/Speech Interaction over Digital Tables by Wrapping Single User Applications”, ICMI '06, Alberta, Canada, Nov. 2-4, 2006.
Tse et al., “Multimodal Multiplayer Tabletop Gaming”, Third international Workshop on Pervasive Gaming Applications—ParGames 2006, Dublin, Ireland, May 7, 2006.
Wallace, “The Semantics of Graphic Input Devices”, ACM SIGGRAPH Computer Graphics, vol. 10, No. 1, 1974, pp. 61-65.
Wellner, Pierre D.., “Adaptive Thresholding fo rthe Digital Desk”, Technical Report, Rank Xerox Research Center, Cambridge Laboratory, Cambridge, United Kingdom (Available online at http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.71,8970&rep=rep1&type=pdf, Jul. 1993, 18 pages.
Wellner, Pierre D., “Self Calibration tor the DigitalDesk”, Technical Report, Rank Xerox Research Centre, Cambridge Laboratory, Cambridge, United Kingdom (Available online at http://citeseerxist/psu.edu/viewdoc/download?doi=10.1.1.44.7371&rep=repl&type=pdt last visited Apr. 22, 2010), Jul. 1993, 16 pages.
Wellner, “The DigitalDesk Calculator Tangible Manipulation on a Desk Top Dispiay”, Proceedings of the ACM Symposium on User Interface Software and Technology (UIST '91) (Available online at http://www.idemployee.id.tue.nl/g.w.m.rauterberg/publications/weliner-91.pdf, last visited Apr. 22, 2010). pp. 27-33.
Westerman, Wayne, “Hand Tracking, Finger Identification Identification and Chordic Manipulation on A Multi-Touch Surface”, Doctoral Dissertation, 1999, 363 Pages.
Westermann et al., “Multi Touch, A New Tactile 2-D Gesture interface for HumanComputer Interaction”, Proceedings of the Human Factors and Ergonomics Society 45th Annual Meeting, Minneapolis, MN, USA, 2001, pp. 632-636.
Wigdor et al., “Effects of Display Position and Control Space Orientation on User Preference and Performance” CHI 2006, Montreal, Quebec, Canada, Apr. 22-27, 2006, pp. 309-318.
Wigdor et al., “Empirical Investigation into the Effect of Orientation on Text Readability in Tabletop Displays”, ECSCW '05 Proceedings in the 9th Conference on European Conference on Computer Supported Cooperative Work. 2005.
Wigdor et al., “Table-Centric interactive Spaces for Real-Time Collaboration”, AVI '06, Venezia Italy, May 23-26, 2006.
Wigdor et al., “Under the Table Interaction”, UIST '06, Montreux, Switzerland, Oct. 15-18, 2006, pp. 259-268.
Wikibooks, “Java Programming/Applets/Event Listeners”, available at <http://en.wikibooks.org/wiki/Java—Programming/Applets/Event—Listeners>, May 1, 2007, 6 pages.
Wilson, “PlayAnywhere: A Compact Interactive Tabletop Projection-Vision System”, UIST '05, Seattle, Washington, USA. Oct. 23-27, 2005.
Wilson, Andrew D.., “TouchLight: An Imaging Touch Screen and Display for Gesture-Based Interaction”, ACM, Oct. 13-15, 2004, 8 pages.
Wireless News, “Adobe Rolls Out Flash Player 9”, Jun. 28, 2006.
Wittenburg et al., “Research on Public, Community, and Situated Displays”, MERL, Cambridge, Public, Community and Situated Displays Workshop (CSCW), Nov. 2002.
Wu et al., “Gesture Registration. Relaxation, and Reuse for Multi-Point”, IEEE International Workshop on Horizontal Interactive Human-Computer Systems, 2006, 8 pages.
Wu et al., “Multi-Finger and Whole Hand Gestural Interaction Techniques for Multi-User Tabletop Displays”. UIST '03, Vancouver, BC, Canada, © ACM 2003, Nov. 5-7, 2003, pp. 193-202.
Youtube, “A Lemurized Formula”, Video uploaded to YouTube by Sph9000, available at <http://www.youtube.com/watch?v=sHAMyQak-LM>, Dec. 15, 2007, 1 page.
Office Action Received for Chinese Patent Application No. 201310073437.3, mailed on Sep. 2, 2015, 18 pages (10 pages of English Translation and 8 pages of Official Copy).
Summon to attend Oral Proceedings received for European Patent Application No. 08712964.9, mailed on May 12, 2016, 6 pages.
Notice of Allowance received for Chinese Patent Application No. 201310073437.3, mailed on May 10, 2016, 4 pages. (2 pages of English Translation and 2 pages of Official Copy).

Related Publications (1)

	Number	Date	Country
	20150248205 A1	Sep 2015	US

Divisions (1)

	Number	Date	Country
Parent	11620717	Jan 2007	US
Child	12869182		US

Continuations (3)

	Number	Date	Country
Parent	14189922	Feb 2014	US
Child	14712637		US
Parent	13867950	Apr 2013	US
Child	14189922		US
Parent	12869182	Aug 2010	US
Child	13867950		US

Application programming interfaces for scrolling operations

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC

International Classifications

Disclaimer

Abstract