This application generally describes applications (such as a web browser) for use on a portable display device including, but not limited to, such a device that include a touch-sensitive display screen.
The popularity of portable devices such as mobile telephones and handheld computing devices such as personal digital assistants (PDAs) continues to increase. These devices generally have a wide variety of capabilities that may include voice communications, electronic mail, calendars, storing contact information and the like. Many of these portable devices offer internet access for web browsing. However, such web browsing is often unsatisfactory because the portable devices generally have small screen sizes and a limited user interface. Such screen size and user interface limitations can also adversely affect the usability of other applications running on the portable devices.
The present application describes an application (such as a web browser) for a portable display device to which inputs are provided using various gestures on a touch-sensitive surface. In a particular, non-limiting example implementation, the portable display device includes two different display screens, at least one of which is a touch screen. By using gestures input to this touch screen, a user can browse the web and control the display of web content on the screen(s) of the portable display device. The gesture inputs may also be used to provide inputs to other applications running on the portable display device.
In addition, the present application also describes a system including a first display screen and a touch-sensitive, second display screen physically separate from the first display screen. A processor is configured to generate respective images for both the first and second display screens, wherein the processor is further configured to interchange images on the first and second display screens in response to a gesture supplied to the touch-sensitive, second display screen.
These and other features and advantages will be better and more completely understood by referring to the following detailed description of exemplary non-limiting illustrative embodiments in conjunction with the drawings of which:
Referring to
A first display screen 32 is recessed within the upper face 26 of the main body 12 with dimensions of approximately 2½ inches in length and 1⅞ inches in width, yielding a diagonal screen dimension of 3 inches. The screen in the exemplary embodiment is a backlit, color liquid crystal display (LCD). This screen is touch sensitive and may be activated by a stylus, described further herein. A power button 34 is located in the upper left corner of face 26 and is used to turn the game device 10 on and off A cross-shaped directional control button 36 is located adjacent and below the power button 34, and is used for game play control.
More specifically, display screen 32 includes a resistive-membrane touch panel that allows coordinates to be obtained in dot units. The touch panel can be operated with a finger or a stylus. The touch panel input data includes x-coordinate (8 bits); y-coordinate (8 bits); touch determination flag (1 bit); and data validity flag (2 bits). In the example portable game system, the touch panel must be pressed down with a force that exceeds a specified value, e.g., 80 g, for the location to be detected. The details of the input data for the touch panel are shown below:
In the upper right corner of the main body 12, there are side-by-side “start” and “select” buttons 38, 40, respectively, with X/Y/A/B buttons 42 located adjacent and below the “start” and select” buttons. Buttons 38, 40 and 42 are also used for game play control. A microphone 44 is located below the left edge of screen 32 for use with specially designed games having a microphone feature. A battery recharge indicator LED 46 and a power indicator LED 48 are also located on the upper face 26, adjacent the lower edge thereof, below the right edge of screen 32.
With reference now especially to
As best seen in
The stylus 71 is a plastic pencil-shaped device with a rounded tip 73 and is used to activate the touch screen 32.
A pair of left, right control buttons (or shoulder buttons) 72, 74 are located on the peripheral edge 30, at the corners where the upper portion 60 of the peripheral edge 30 meets the side portions 76, 78 of the peripheral edge. The location of these buttons and the location of previously described buttons 34, 36 and 42 facilitate manipulation game control by the user's thumbs and index fingers when the game is held with two hands in a natural and intuitive manner.
The lower (or outer) face 28 of the main body is provided with a battery cover 80 (
The cover body 14 also has an upper (or inner) face 82 (
An example geometry engine has the following features:
An example rendering engine has the following features:
The example portable game machine includes various memories. System ROM 712 for the ARM9 core is 8 KB (2K×32 bit) and system ROM 704 for the ARM7 core is 16 KB (4K×32 bit). Internal work RAM 716 shared by the ARM9 and the ARM7 is 32 KB (8K×32 bit) and ARM7 dedicated work RAM 718 is 64 KB (16K×32 bit). There is a total of 656 KB of VRAM 720, i.e., VRAM A to VRAM I (128 KB+128 KB+128 KB+128 KB+64 KB+16 KB+16 KB+32 KB+16 KB).
The on-board wireless communication circuit 722 is capable of using, for example, the 2.4 GHz bandwidth. The following modes are available:
Additional details of the operation of the game device 10 may be found in application Ser. No. 11/127,297, the contents of which are incorporated herein.
Specifically, the operating switch section 814 includes operating switches 814a and 814b, a cross direction keypad 814c, a start switch 814d, and a select switch 814e. The operating switches 814a and 814b are provided on the top surface of the lower housing 818a so as to be located to the right of the first LCD 811. The cross direction key pad 814c, the start switch 814d, and the select switch 814e are provided on the top surface of the lower housing 818a so as to be located to the left of the first LCD 811. The operating switches 814a and 814b are used for inputting instructions to jump, punch, operate a weapon, and so on in an action game, or inputting instructions to obtain an item, select and determine a weapon or a command, and so on in a role playing game (RPG) such as a simulation RPG. The cross direction keypad 814c is used for indicating a moving direction on a game screen, e.g., a direction to move a player object (or a player character) which can be operated by the player, or a direction to move a cursor. If necessary, additional operating switches may be provided, or side switches 814f and 814g may be provided respectively on right and left sides of the upper side surface of the lower housing 818a as shown in
Further, a touch panel 813 is provided on the first LCD 811 (as indicated by broken lines in
The upper housing 818b has a storage hole 815b (indicated by two-dot dashed lines in
An internal structure of the game device 800 is described now with reference to
In
The cartridge 817 is detachably connected to the connector 928. As described above, the cartridge 817 is a storage medium having a program stored therein, and specifically includes a ROM 971 in which the program is stored and a RAM 972 for storing backup data in a rewritable manner. The program stored in the ROM 971 of the cartridge 817 is loaded to the WRAM 922, and then implemented by the CPU core 921. The WRAM 922 stores temporary data obtained by the CPU core 921 implementing the program or data for generating images.
The I/F circuit 927 is connected to the touch panel 813, the operating switch section 914, and the loudspeaker 915. The loudspeaker 915 is located behind a portion of the lower housing 818a where the sound holes 815b are formed. A wireless communication circuit (not shown) may also be provided.
The first GPU 924 is connected to a first video RAM (VRAM) 923, and the second GPU 926 is connected to a second VRAM 925. The first GPU 924, responsive to an instruction from the CPU core 921, generates a first image (such as a game image or web page image) based on data for generating an image stored in the WRAM 922, and renders the generated image on the first VRAM 923. The second GPU 926, responsive to an instruction from the CPU core 921, generates a second image (such as a game image or web page image) based on data for generating an image stored in the WRAM 922, and renders the generated image on the second VRAM 925.
The first VRAM 923 is connected to the first LCD 811, and the second VRAM 925 is connected to the second LCD 812. The first GPU 924 outputs the first image rendered on the first VRAM 923 to the first LCD 811. The first LCD 811 displays the first image outputted from the first GPU 924. The second GPU 926 outputs the second image rendered on the second VRAM 925 to the second LCD 812. The second LCD 812 displays the second image outputted from the second GPU 926.
Additional details regarding the above-described game apparatuses may be found in U.S. Publication Nos. 2005-0227761; 2005-0164794; and 2005-0159223 and application Ser. Nos. 10/921,921 and 11/127,297, the contents of each of which are incorporated herein in their entirety.
As noted above, the example portable display devices include wireless communication circuitry that enables wireless communication with, among other things, wireless LAN access point(s). These wireless access points can provide, among other things, a connection to the Internet. The access points may be provided in public areas (e.g., stores, libraries, sports arenas, stadiums, public transportation vehicles such as buses and trains, airplanes, etc.) or in offices or homes. For example, in a home environment, the access point may be embodied as a computer that is connected to the Internet via, for example, a dial-up connection or a cable modem. In alternative implementations, wireless or wired communication circuitry may be connected to the portable display device via one of cartridge slots (e.g., slot 58 or slot 64). For example, the communication circuitry may be embodied in a cartridge adapted to fit in one of these slots. This communication circuitry may, for example, connect by wired link to the public switched telephone network or to a local area network to thereby provide Internet access. In other implementations, the communication circuitry may wirelessly connect to a base station of a mobile telephone network through which a connection to the Internet may be established.
Various applications may utilize the gesture inputs described in detail below. The example application described herein is a web browser program that is executed by the processing circuitry of the portable display device and may be permanently stored in on-board memory of the portable display device. In this case, the web browser program may be identified on a menu or by an icon when the portable display device is turned on. The browser may be executed by selecting it from the menu or by selecting the icon. Alternatively, the browser program may stored in a memory device on a cartridge connected to the portable display device via one of the slots 58 and 64.
Generally speaking, the example web browser program accesses web servers on the Internet using the hypertext transport protocol (HTTP), obtains data from the servers, processes the data in accordance with its type (e.g., text, images, etc.), and displays, if necessary, after laying the data out to fit the screen(s). The web browser program may use the two LCD screens 32 and 88 (or 811 and 812) described above, thus achieving a multi-window display.
The web browser program described herein (as well as other applications) may be implemented in software executable by a processing circuitry of the portable display device, e.g., as a set of instructions (program code) in a code module resident in a random access memory accessible to the processing circuitry. Until required by the processing circuitry, the set of instructions may be stored in another memory (e.g., in a memory card removably connectable to the portable display device) or may be downloaded via the Internet or other computer network.
The web browser program allows quick and easy navigation via gestures made with a stylus on touch panel 32 (or 813). These gestures include a “slide up” gesture in which the stylus (or other pointing device such as a user's finger) is brought into contact with the touch panel 32 and then moved or dragged (slid) in an upward direction. Similarly, a “slide down” gesture may be performed by bringing the stylus into contact with the touch panel 32 and then moving the stylus in a downward direction. “Slide right” and “slide left” gestures may be performed by bringing the stylus into contact with the touch panel 32 and then moving the stylus in a rightward or leftward direction, respectively. Other gestures may be developed which are combinations of the aforementioned gestures. For example, one gesture may be comprised of the “slide up” gesture followed by the “slide down” gesture and another gesture may be comprised of the “slide down” gesture followed by the “slide up” gesture. Similarly, one gesture may be comprised of the “slide right” gesture followed by the “slide left” gesture and another gesture may be comprised of the “slide left” gesture followed by the “slide right” gesture.
Of course, the above-described gestures are provided by way of example only and it will be appreciated that other gestures may be developed and utilized based on the description herein.
The input gestures may be recognized in accordance with a routine provided as part of the web browser program. Alternatively, a separate gesture recognition routine or application may be provided for recognizing the gesture based on the path of the stylus (or finger) on the touch panel 32 and providing data indicative of the recognized gesture to the web browser program. Generally speaking, the recognition may be performed based on comparisons between input gestures and a gesture recognition database stored in memory accessible to the processing circuitry of the portable display device.
The following sections explain the operations a user can perform with the touch panel 32 of portable display device 10. Clearly similar operations may be performed with the other example portable display devices.
1.1 Touch Panel Area
In an example implementation of the web browser program, the touch panel 32 is divided into the following areas. The program performs its processes in response to the area that the user touches.
1.2 Touch Screen Input Mode
The user can switch the input mode of the touch screen 32 by, for example, selecting an input mode from the menu. In other instances, the input mode may be switched automatically as needed by the program. In some example implementations, the cursor characteristics (shape, color, size, etc.) may vary depending on the input mode.
1.3 Actions
When the user operates touch screen 32, the example web browser program processes the input first of all according to the area where it is touched, and by the input mode of the touch screen and according to the gestures as described below.
1.3.1 Select Mode
When the stylus input mode is in the select mode, the web browser program operates as follows. When the web browser program starts and nothing has been input, the program will be in this mode.
After an area is touched and the example web browser program starts executing the corresponding operation, even if another area is entered, for example, during sliding, the operation does not change.
1.3.2 Zoom Mode
When the stylus input mode is in the zoom mode, the example web browser program processes inputs as follows:
1.3.3 Scroll Mode
When the stylus input mode is in the scroll mode, the example web browser program processes as follows.
1.3.4 if a Menu Icon has been Touched (Same in all Modes)
When a menu icon is touched, the example web browser program acts the same in all modes. Until a pop-menu displayed is closed, touching a menu icon area will not cause anything to happen.
1.4 Menu
An example menu may have the following items, touching each of which causes the process allocated to it to be executed.
1.4.1 Navigation
When Stop, Previous Page, Next Page, Default Page, Reload or Input URL is selected, the corresponding URL is displayed.
1.4.2 Bookmarks
When Register Bookmark is selected, a dialog box comes up prompting the user to register a bookmark. If OK is selected, the current URL is registered and saved in the bookmarks section. If Cancel is selected, the Register Bookmark dialog box closes. If Refer to Bookmarks is selected, the Bookmark Menu is displayed. The Bookmark Menu is displayed in a window with a scroll bar. If a bookmark is touched, the web browser program obtain the web page corresponding to that URL.
If there are so many menu items they cannot be displayed in a window, the scroll bar can be used to change what is being displayed.
1.4.3 Changing the Touch Screen Input Mode
When the Switch Touch Screen Mode icon is touched, a sub-menu pops up and the user can select from among the Select Mode, Scroll Mode and Zoom Modes.
1.4.4 Properties Page
The Properties Page displays a dialog box which can be used to make settings such as user information, internet provider, etc.
1.4.5 Close Menu
The menu closes if the menu popup/down icon is touched. The following functions may also be provided.
Character String Input
An input function can use the touch screen so that input can be made via handwriting or with an on-screen keyboard.
Image Input
Symbol data (vector, raster) can be input.
Multi-Boot
Using a multi-boot function, a service can be provide in which a user can simultaneously download the browser software and the desired home page.
Extended Function
Will permit websites compatible with the browser to realize functions that cannot be achieved by other browsers by executing original scripts written for the portable device 10.
MIME Type
Browser unique applications
XHTML Extended Tags
Extends tags using XHTML, achieving operations unique to portable device 10.
Upper Screen Copy Anchor Tags
When links that are defined with these tags are touched, they are displayed in the upper screen. This would make it possible, for example, if the content were a picture book and if a link were attached to a picture corresponding to some text, when the text was touched, the picture would be displayed in the upper screen.
Dictionary Search Anchor Tag
Using this tag, highlighted text would be looked up from a preset dictionary site and the results would be displayed in the upper screen.
Text Search Mode
A special mode for searching and perusing text. In this mode, when a character string is selected with the stylus, if it is slid up (i.e., a “slide up” gesture in which the stylus (or other pointing device) is brought into contact with the character string and the stylus is then moved upward on the screen), a search request is sent out for that word to the preset search or dictionary site and the results are displayed on the upper screen. If it is slid down (i.e., a “slide down” gesture in which the stylus (or other pointing device) is brought into contact with the character string and the stylus is then moved downward on the screen), the search results are displayed in the lower screen while the currently displayed page is displayed in the upper screen.
Game Download Function
Games can be downloaded and played.
Agent Function
Various agents can be downloaded and used.
The following additional example functions and operations may be utilized in a web browser program.
1) If a user touches a link displayed on the lower screen and slides it upward, the web page for the linked URL will be displayed on the upper screen.
2) If a user touches a link displayed on the lower screen, slides it upward and then downward, the web page for the linked URL will be displayed on the lower screen and the screen previously displayed on the lower screen will be displayed on the upper screen.
3) If a user touches a position other than a link on the lower screen and slides it upward, the screen displayed on the lower screen will be copied and displayed on the upper screen.
4) If a user touches a position other than a link on the lower screen, slides it upward and then downward, a screen displayed on the lower screen will be switched with the one displayed on the upper screen.
5) If a user touches a position other than a link on the lower screen and slides it downward, a screen displayed on the upper screen will be copied and displayed on the lower screen.
6) If a user touches a position other than a link on the lower screen and slides it to the left, the user will be able to go back to the last page.
7) If a user touches a position other than a link on the lower screen and slides it to the right, the user will be able to go to the next page.
8) If a user touches an image and slides it upward, a magnified image will be displayed on the upper screen.
9) If a user slides a tab downward, a corresponding screen will be displayed on the lower screen.
10) If a user slides a tab downward and then upward, a screen displayed on the upper screen will be switched with the one on the lower screen, which respectively correspond to the tab.
11) If a user circles a field by using a stylus on the lower screen and slide it upward, the field will be magnified and displayed on the upper screen.
12) Setting up a tab that will be displayed on the upper screen when touched.
Some of the above-described functions and operations are discussed below with reference to
The menu section 1010 include various icons 1015a-1015j. The functions/processes associated with these icons may be invoked by touching the icons with the stylus.
Icon 1015a is a “switch stylus modes” icon that, when touched, causes a sub-menu to pop up from which the user can select from among the Select, Scroll and Zoom modes. In an alternative implementation, touching the icon 1015a a first time sets the Select mode, touching a second time sets the Scroll mode, touching a third time sets the Zoom mode, touching a fourth time sets the Select mode, etc.
Icon 1015b is a “stop downloading” icon that, when touched, stops any current downloading of a web page.
Icon 1015c is a “previous page” icon that, when touched, causes display of a previous web page. If the user is at the first page, touching icon 1015c has no effect.
Icon 1015d is a “next page” icon that, when touched, causes display of a next web page. If the user is at the last page, touching icon 1015d has not effect.
Icon 1015e is “home page” icon that, when touched, causes a home (default) page to be downloaded. An initial home page setting may be made at the time of installing the web browser program, and the user may modify this setting using, for example, a “settings” function.
Icon 1015f is a “reload” icon that, when touched, causes the current web page to be reloaded.
Icon 1015g is an “input URL” icon that, when touched, causes a screen (or screens) to be displayed to permit a user to input an URL either using an on-screen keyboard or by handwriting.
Icon 1015h is a “Go to Bookmarked Page” icon that, when touched, causes a list of bookmarked web pages to displayed from which the user can select.
Icon 1015i is a “Register Bookmark” icon that, when touched, causes the current web page to be added to the list of bookmarked pages.
Icon 1015j is a “Settings” icon that, when touched, causes display of a screen (or screens) that a user can use to set various browser properties (e.g., home page, security settings, and the like).
Of course, other implementations that include different icons may be used. In one implementation, the user can use the “Settings” function to determine the order and presence/absence of various icons on the menu display.
Tab area 1020 includes a plurality of tabs each associated with one of one or more screens for display on the upper screen. When one of the tabs is touched, the web page associated with that tab is displayed on the upper screen. When one of the tabs is slid down, the web page associated with that tab is displayed on the lower screen. When one of the tabs is slid down and then up, the web page corresponding to that tab is displayed on the lower screen and the web page currently displayed on the lower screen is displayed on the upper screen.
Link area 1030 contains for example a link to a web page. When the link is touched, the web page associated with the link is displayed on the lower screen. When the link is slid upward, the web page associated with the link is displayed on the upper screen. When the link is slid upward and then downward, the web page associated with the link is displayed on the lower screen and the web page currently displayed on the lower screen is moved to the upper screen.
“Other” area 1040 may also be used to perform operations using drawn gestures. For example, sliding right on the other area 1040 causes a “next” web page to be displayed. Sliding left on the other area 1040 causes a “previous” web page to be displayed. Sliding up on the other area 1040 copies the web page currently displayed on the lower screen to the upper screen. Sliding down on the other area 1040 copies the web page currently displayed on the upper screen to the lower screen. Sliding up and then down on the other area 1040 switches the displays on the upper and lower screens. Sliding left and then right cancels an operation.
As noted in
As shown in
As further shown in
While the gesture inputs have been described above in the context of a web browser, other implementations are possible. For example, text screens for providing help for applications running on the portable display system may include various pages with associated links and such text screens may also be manipulated using the gestures described above. In addition, the gestures described herein may be used for manipulating the displays on the upper and lower screens for other types of content. For example, a user watching a movie on the lower screen may slide up on the lower screen to cause the movie to be displayed on the upper screen. The movie may be returned to the lower screen by sliding up and then down.
Similarly, the game displays on the upper and lower screens may be controlled using gestures. For example, a game may provide different game scenes on the upper and lower screens. A player can, for example, provide touch-screen inputs to the scene on the lower screen and, upon the occurrence of a certain event in the game, use a gesture input to interchange the upper and lower screens, thereby enabling touch-screen inputs to be supplied to the scene that was originally on the upper screen.
Note that although an exemplary liquid crystal display section for simultaneously display two separate images has been described above with respect to a case where the two LCDs (e.g., 811 and 812) are arranged so as to be physically separated in a vertical direction, the LCDs 811 and 812 may be arranged side by side in a horizontal direction without using the upper housing. In order to arrange the LCDs side by side in a horizontal direction, as shown in
Further, instead of arranging the LCDs 811 and 812 so as to be physically separated in a vertical direction, an LCD 811a having a length twice the length of the LCD 811 and the same width as that of the LCD 811 as shown in
While the above examples have been described with reference to a portable display device with a touch-sensitive display screen, other implementations may use a touch pad separate from a display screen.
While the technology herein has been described in connection with exemplary illustrative non-limiting embodiments, the invention is not to be limited by the disclosure. For example, the browser may be executed on portable devices other than the portable device described above, including mobile telephones, personal digital assistants, hand-held game devices, personal computers, laptop computers, and the like. By way of example,
One or more speakers 1517 are connected to system bus 1507 via an audio interface 1519 to output sounds. A communication circuit 1521 is connected to system bus 1507 via a communications interface 1523 to permit communication with other devices. By way of illustration, communication circuit 1521 may, for example, be a modem and communications interface 1523 may be a serial port. Generally speaking, communication circuit 1521 may be configured for wired or wireless communication in accordance with any conventional communication protocol. A power supply 1525 provides power for the components of system 1501.
This application is intended cover all corresponding and equivalent arrangements whether or not specifically disclosed herein.
This application is a continuation of application Ser. No. 16/400,966, filed on May 1, 2019, now U.S. Pat. No. 10,996,842, which is a continuation of application Ser. No. 14/548,103, filed on Nov. 19, 2014, now U.S. Pat. No. 10,324,615, which is a continuation of application Ser. No. 13/355,545, filed Jan. 22, 2012, now abandoned, which is a continuation of application Ser. No. 11/253,793, filed Oct. 20, 2005, now U.S. Pat. No. 8,169,410, which claims the benefit of provisional Application No. 60/619,952, filed Oct. 20, 2004. The contents of each of these applications are incorporated herein in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
4751669 | Sturgis | Jun 1988 | A |
4873662 | Sargent | Oct 1989 | A |
5166666 | Tanaka | Nov 1992 | A |
5252951 | Tannenbaum | Oct 1993 | A |
5347477 | Lee | Sep 1994 | A |
5463725 | Henckel | Oct 1995 | A |
5467102 | Kuno | Nov 1995 | A |
5471578 | Moran | Nov 1995 | A |
5564005 | Weber | Oct 1996 | A |
5592607 | Weber | Jan 1997 | A |
5612719 | Beernink | Mar 1997 | A |
5694162 | Freeny, Jr. | Dec 1997 | A |
5717939 | Bricklin | Feb 1998 | A |
5809267 | Moran | Sep 1998 | A |
5847698 | Reavey | Dec 1998 | A |
5880743 | Moran | Mar 1999 | A |
5893132 | Huffman | Apr 1999 | A |
5900848 | Haneda | May 1999 | A |
5990893 | Numazaki | Nov 1999 | A |
6020881 | Naughton et al. | Feb 2000 | A |
6025844 | Parsons | Feb 2000 | A |
6037937 | Beaton | Mar 2000 | A |
6057845 | Dupouy | May 2000 | A |
6068188 | Knowles | May 2000 | A |
6088731 | Kiraly et al. | Jul 2000 | A |
6091409 | Dickman | Jul 2000 | A |
6133916 | Bukszar | Oct 2000 | A |
6249606 | Kiraly et al. | Jun 2001 | B1 |
6297945 | Yamamoto | Oct 2001 | B1 |
6313853 | Lamontagne | Nov 2001 | B1 |
6331840 | Nielson | Dec 2001 | B1 |
6396523 | Segal et al. | May 2002 | B1 |
6438580 | Mears | Aug 2002 | B1 |
6442578 | Forcier | Aug 2002 | B1 |
6486895 | Robertson | Nov 2002 | B1 |
6525749 | Moran et al. | Feb 2003 | B1 |
6545669 | Kinawi et al. | Apr 2003 | B1 |
6639584 | Li | Oct 2003 | B1 |
6721721 | Bates | Apr 2004 | B1 |
6725203 | Seet et al. | Apr 2004 | B1 |
6735632 | Kiraly et al. | May 2004 | B1 |
6765557 | Segal et al. | Jul 2004 | B1 |
6859909 | Lerner et al. | Feb 2005 | B1 |
7084859 | Pryor | Aug 2006 | B1 |
7221330 | Finke-Anlauff | May 2007 | B2 |
7249315 | Moetteli | Jul 2007 | B2 |
7430524 | Shah | Sep 2008 | B2 |
7489303 | Pryor | Feb 2009 | B1 |
7543240 | Harrison | Jun 2009 | B2 |
7573462 | Ouchi | Aug 2009 | B2 |
7750893 | Hashimoto et al. | Jul 2010 | B2 |
7804489 | Guiter | Sep 2010 | B1 |
8089423 | Harris | Jan 2012 | B1 |
8169410 | Hashimoto et al. | May 2012 | B2 |
8185604 | Forrester | May 2012 | B2 |
8479122 | Hotelling | Jul 2013 | B2 |
9052816 | Hashimoto et al. | Jun 2015 | B2 |
10324615 | Hashimoto et al. | Jun 2019 | B2 |
10996842 | Hashimoto et al. | May 2021 | B2 |
20010019324 | Rosenberg | Sep 2001 | A1 |
20010035860 | Segal | Nov 2001 | A1 |
20010045949 | Chithambaram | Nov 2001 | A1 |
20020015064 | Robotham | Feb 2002 | A1 |
20020033795 | Shahoian | Mar 2002 | A1 |
20020047866 | Matsumoto | Apr 2002 | A1 |
20020097229 | Rose | Jul 2002 | A1 |
20020124022 | Yoo | Sep 2002 | A1 |
20020138626 | Smith | Sep 2002 | A1 |
20020151283 | Pallakoff | Oct 2002 | A1 |
20020158812 | Pallakoff | Oct 2002 | A1 |
20020163545 | Hii | Nov 2002 | A1 |
20030048250 | Boon | Mar 2003 | A1 |
20030156145 | Hullender | Aug 2003 | A1 |
20030197744 | Irvine | Oct 2003 | A1 |
20030222917 | Trantow | Dec 2003 | A1 |
20030227423 | Arai | Dec 2003 | A1 |
20040056837 | Koga | Mar 2004 | A1 |
20040108968 | Finke-Anlauff | Jun 2004 | A1 |
20040138792 | Foxford | Jul 2004 | A1 |
20040141011 | Smethers | Jul 2004 | A1 |
20040141016 | Fukatsu | Jul 2004 | A1 |
20040141649 | Landstad | Jul 2004 | A1 |
20040145574 | Xin | Jul 2004 | A1 |
20040169683 | Chiu | Sep 2004 | A1 |
20040174399 | Wu | Sep 2004 | A1 |
20050012723 | Pallakoff | Jan 2005 | A1 |
20050034063 | Baker | Feb 2005 | A1 |
20050055627 | Lloyd | Mar 2005 | A1 |
20050064936 | Pryor | Mar 2005 | A1 |
20050093868 | Hinckley | May 2005 | A1 |
20060010400 | Dehlin | Jan 2006 | A1 |
20060026521 | Hotelling | Feb 2006 | A1 |
20060036955 | Baudisch | Feb 2006 | A1 |
20060101354 | Hashimoto et al. | May 2006 | A1 |
20060248061 | Kulakow | Nov 2006 | A1 |
20090327976 | Williamson | Dec 2009 | A1 |
20120124491 | Hashimoto et al. | May 2012 | A1 |
Number | Date | Country |
---|---|---|
05-127819 | May 1993 | JP |
07-294892 | Nov 1995 | JP |
08-076926 | Mar 1996 | JP |
2000-010655 | Jan 2000 | JP |
2000-163193 | Jun 2000 | JP |
3095145 | Aug 2000 | JP |
2001-005438 | Jan 2001 | JP |
2002-091688 | Mar 2002 | JP |
2003280622 | Oct 2003 | JP |
2003330588 | Nov 2003 | JP |
0034942 | Jun 2000 | WO |
Entry |
---|
Office Action dated Jan. 16, 2015 in U.S. Appl. No. 14/548,080. |
Notice of Allowance and Fee(s) Due and Notice of Allowability dated Mar. 12, 2015 in U.S. Appl. No. 14/548,080. |
Willey, “Design and Implementation of a Stroke Interface Library”, Internet Article, Mar. 24, 1997, 6 pages, IEEE Region 4 Student Paper Contest, http://citeseer.ist.psu.edu/cache/papers/cs/24072/http:zSzzSzwww.etla.netzSzlibstokezSzlibstroke.pdf/willey97design.pdf. |
Worth, “xstroke: Full-screen Gesture Recognition for X”, Proceedings of the Freenix Track: 2003 Usenix Annual Technical Conference, Jun. 9, 2003, pp. 187-196, http://www.usenix.org/events/usenix03/tech/freenix03/full_papers/worth/worth.pdf. |
Moyle et al., “A Flick in the Right Direction: An Evaluation of Simple Gesture Based Controls”, Nov. 2, 2001, 47 pages. |
Motion Gestures in Opera (downloaded from internet on Mar. 15, 2005 at http://www.opera.com/features/mouse/). |
Opera FAQ (downloaded from internet on Mar. 15, 2005 at http://www.opera.com/features/mouse/). |
English-language machine translation of JP 05-127819. |
English-language machine translation of JP 07-294892. |
English-language machine translation of JP 08-076926. |
English-language machine translation of JP 2000-010655. |
English-language machine translation of JP 2000-163193. |
English-language machine translation of JP 2001-005438. |
English-language machine translation of JP 2002-091688. |
“Avant Browser Help—Mouse Gestures,” http://www.avantbrowser.com (1999-2000). |
Hansen, Evan, “Building a better computer mouse,” http://news.com (Oct. 2, 2004). |
“Mouse Gestures,” http://mozdev.org (Oct. 27, 2004). |
Todd, Christopher, “Mouse gestures @ Penn State Physics,” www.phys.psu.edu (2003). |
Christodd, “Mouse Gestures—Controlled by Motion,” www.bitesizeinc.net (Dec. 10, 2003). |
“Mouse Gestures for Internet Explorer—The Gestures,” www.ysgyfarnog.co.uk. |
“Mouse Gestures in Opera,” http://www.opera.com. |
“Deepnet Explorer, Quick Tour, 5. Mouse Gestures,” http://www.deepnetexplorer.com (2004). |
Buxton, William A.S., “Two-Handed Document Navigation,” XEROX Disclosure Journal, 19(2), Mar./Apr. 1994, 103-108, www.billbuxton.com. |
Hashitmoto et al., U.S. Appl. No. 11/253,793, filed Oct. 20, 2005, now U.S. Pat. No. 8,169,410. |
Hashitmoto et al., U.S. Appl. No. 13/355,545, filed Jan. 22, 2012, now abandoned. |
Hashitmoto et al., U.S. Appl. No. 14/548,080, filed Nov. 19, 2014, now U.S. Pat. No. 9,052,816. |
Hashitmoto et al., U.S. Appl. No. 14/548,103, filed Nov. 19, 2014, U.S. Pat. No. 10,324,615. |
Hashitmoto et al., U.S. Appl. No. 16/400,966, filed May 1, 2019. |
Number | Date | Country | |
---|---|---|---|
20210248306 A1 | Aug 2021 | US |
Number | Date | Country | |
---|---|---|---|
60619952 | Oct 2004 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16400966 | May 2019 | US |
Child | 17244766 | US | |
Parent | 14548103 | Nov 2014 | US |
Child | 16400966 | US | |
Parent | 13355545 | Jan 2012 | US |
Child | 14548103 | US | |
Parent | 11253793 | Oct 2005 | US |
Child | 13355545 | US |