Systems and methods for handwriting to a screen

Abstract

Systems and methods are described that enable handwriting into a data-entry field on a screen without independently selecting that data-entry field. These systems and methods can also provide a handwriting guide geographically associated with a data-entry field into which a user is intending to write that permits substantially all of a computing device's screen to be viewed.

Description

TECHNICAL FIELD

This invention relates to handwriting made to screens.

BACKGROUND

Many computing devices, such as hand-held computers, PDAs, and Palm Pilots™, enable users to enter text and commands by handwriting over the device's screen. Ink recognition software can convert this handwriting into text or a command that the device can understand.

Prior to enabling handwriting into a particular data-entry field, these devices often require that a user independently select the data-entry field into which the handwriting text is to be entered. A user can select the data-entry field with a writing gesture called “tapping”, after which the device can enable handwriting of text into the selected data-entry field. This and similar requirements make these devices less intuitive and hence, more difficult for new users to use. That is, many users are most comfortable with handwriting on a paper medium, not computing devices. The more user-intuitive paper medium does not require a user to tap a field on a page in order to write into that field.

As noted above, once a data-entry field is selected on a computing device, such as by “tapping” on the field, the device typically enables a user to enter text into the selected data-entry field. To guide the user's handwriting, some devices have a screen area, often a narrow rectangle at the bottom, into which a user can write. Handwriting made into this writing area can be entered as text into the data-entry field. This writing area, however, can be geographically unassociated with the data-entry field into which the user is attempting to enter text. That is, in many systems, this writing area is limited to a particular geographic location, while the data-entry field can be anywhere on the screen.

This disjoint or non-logical association between the data-entry field and where the user actually writes can reduce the user's ability to mentally retain the field's context. The user may want to view or otherwise ascertain the information currently in or surrounding the data-entry field when handwriting in the writing area. To view or ascertain such information, the user may have to change his or her focus from the writing area to the data-entry field and its context. Needless to say, this can be distracting.

Additionally, the area allotted for handwriting can be quite small. Especially for devices with fairly small screens, having a small portion of that screen for handwriting can make handwriting difficult. A small area, for example, can make it difficult for a user to write large enough for ink recognition software to convert the handwriting to text. And, a small area can restrict how much a user can write at once, potentially slowing or causing the user to lose his or her train of thought.

Some other computing devices enable a user to enter text into a previously selected data-entry field by handwriting anywhere over the device's screen. Allowing a user to write anywhere on a screen can cause numerous problems. First, it can confuse users because the location at which the user writes can be geographically unassociated with the field, thus facilitating a user's forgetting which field was originally selected. Once the user begins to write, for instance, they can get distracted and mentally lose track of the selected field. Second, when a user is not given guidance in terms of acceptable character size, he or she may write too large or too small. A user may, for instance, attempt to write or cram everything inside a data-entry field that may simply be too small to accommodate all that the user intends to write. Small handwriting can be difficult for ink recognition software to recognize and may also be a strain on the user. On the other hand, handwriting that is too large can cause a user to run out of room on the screen. Third, allowing users to write anywhere can permit them to write at an angle which, in turn, may cause ink recognition software problems insofar as the ability to recognize tilted handwriting is concerned.

Still other computing devices can enable a user to enter text into a previously selected data-entry field via a pop-up window. When a user selects the data-entry field, the device can pop up a window, usually just below the field. This pop-up window, however, can obscure part of the screen. By so doing, the window can obscure features and information that a user might need. For example, if a user wants to write notes for a 9 a.m. meeting into his or her day-timer and needs to concurrently see what he or she has to do at 10 a.m., for instance, the pop-up window may prevent the user from seeing this information by obscuring the 10 a.m. field.

SUMMARY

Systems and methods are described that enable handwriting into a data-entry field on a computing device's screen without independently selecting that data-entry field. In some embodiments, these systems and methods provide a handwriting guide geographically associated with a data-entry field into which a user is intending to write that permits substantially all features of a computing device's screen to be viewed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an exemplary architecture having a computing device and exemplary applications.

FIG. 2 sets forth a flow diagram of an exemplary process for enabling a user to write into a data-entry field.

FIG. 3 illustrates an exemplary data-entry form and screen shot, the screen shot showing the data-entry form after handwriting has been received and displayed.

FIG. 4 illustrates the exemplary screen shot of FIG. 3 and a blow-up of the screen shot showing handwriting.

FIG. 5 sets forth a flow diagram of an exemplary process for presenting and generating a handwriting guide.

FIG. 6 illustrates an exemplary screen shot showing an exemplary handwriting guide.

FIG. 7 illustrates an exemplary screen shot showing the exemplary handwriting guide of FIG. 6 having an altered size and additional handwriting.

FIG. 8 illustrates an exemplary screen shot showing text converted from handwriting and entered into a data-entry field.

The same numbers are used throughout the disclosure and figures to reference like components and features.

DETAILED DESCRIPTION

Overview

Systems and methods (“tools”) described below can, in at least some embodiments, enable a user to write text into a data-entry field on a computing device's screen without independently selecting that data-entry field. These tools can determine, based on a user's handwriting, a data-entry field in which to enter the handwriting. Enabling users to write into data-entry fields without independently selecting a field can make their experience more intuitive and user-friendly.

The tools can also, in some embodiments, provide a handwriting guide capable of guiding a user's handwriting. The handwriting guide is geographically associated with a data-entry field into which the user is intending to write. In at least some embodiments, the handwriting guide permits substantially all features of a computing device's screen to be viewed during the act of writing. The handwriting guide can help a user keep track of the field, guide the user's handwriting so that it can more easily be read by ink recognition software, and permit the user to view information on the screen.

Exemplary Architecture

Referring to FIG. 1, an exemplary system/architecture 100 is shown having an exemplary computing device 102, tablet screen 104, stylus 106, data-entry form 108, ink recognition application 110, guide application 112, and auto-selector 114. This architecture 100 and its components are shown to aid in discussing the tools but are not intended to limit their scope or applicability.

The computing device comprises hardware and software capable of communicating with or executing the ink recognition application, the guide application, and/or the auto-selector. The computing device is also capable of communicating with a user through the tablet screen. The tablet screen is capable of presenting the data-entry form to a user and receiving input from the user, such as through the user handwriting over the tablet screen with the stylus.

The ink recognition application is capable of converting handwriting into text or commands recognizable by the computing device, the guide application, or the auto-selector. The guide application and the auto-selector can operate separately or in combination and comprise computer-readable media executable by a computing device, such as computing device 102, that perform various acts described below.

Enabling a User to Write into a Field

Referring to FIG. 2, an exemplary process 200 for enabling a user to write into a data-entry field is shown. The process 200 is illustrated as a series of blocks representing individual operations or acts performed by auto-selector 114. This and other processes described herein may be implemented in any suitable hardware, software, firmware, or combination thereof. In the case of software and firmware, these processes represent sets of operations implemented as computer-executable instructions.

At block 202, the auto-selector receives handwriting indicia. This handwriting indicia can comprise indicia for handwriting strokes recognizable as text input from a user, such as a character or word. The auto-selector can receive the handwriting indicia from various devices or software, such as directly from tablet screen 104 or through ink recognition application 110.

As an example, consider FIG. 3. There, data-entry form 108 and a screen shot 300 showing the data-entry form after handwriting 302 has been received and displayed over the form is shown. Here, the handwriting is a single stylus stroke received from a user through tablet screen 104. In another embodiment, the handwriting is received from a user through another device, such as a light pen or a mouse that enables handwriting to be made to a screen without necessarily requiring a user to handwrite over that screen. The received stroke is part of a character rather than a gesture, as will become apparent below. A gesture, as used in this document, constitutes a non-writing-based input from a user that is recognizable as a command rather than text. For example, the “tap” described in the Background section above is one example of a gesture.

At block 204 (FIG. 2), the auto-selector determines, responsive to the handwriting received, a data-entry field in which to enter the handwriting. The auto-selector can determine which data-entry field to enter the handwriting based on a geographic relation between the handwriting and the data-entry field. This geographic relation can be based on which data-entry field the handwriting intersects, which it intersects first or most often if there are multiple fields intersected, which field is closest to the handwriting, and the like. Alternately or additionally, a small or first-received portion of the handwriting, such as the first stroke or character, can be analyzed to determine in which field to enter the handwriting. By so doing, the auto-selector can determine the field more quickly than if it waits to receive multiple strokes or characters.

Continuing the illustrated example, FIG. 4 shows screen shot 300 of FIG. 3 and an enlarged portion 400 of the screen shot which shows handwriting 302. In this illustrated example, the auto-selector determines a data-entry field in which to enter the handwriting based on the first stroke made by a user. In the illustrated and described embodiment, the auto-selector employs a bounding-type algorithm to assist in making this determination.

As but one example of a bounding-type algorithm, consider the following. First, the auto-selector computes a bounding shape 402 for the handwriting. In this particular example, the bounding shape comprises a rectangle—although any suitable shape can be used. Second, the auto-selector compares the bounded writing area occupied by the bounding rectangle against areas occupied by data-entry fields of data-entry form 108, such as a meeting subject field 404 and a meeting organizer field 406. In one embodiment, the auto-selector compares the bounding rectangle only against fields' geometries that are configured to accept text and which are currently viewable by the user. In the illustrated example, about forty percent of the bounding rectangle overlaps with the area occupied by the meeting subject field and no area overlaps with the meeting organizer field. Third, the auto-selector compares the overlapping areas, picking the field with the largest overlap (here the meeting subject field). If there is no overlap with a field, the auto-selector can pick the field closest to the bounding rectangle or use additional handwriting and perform the algorithm again.

Returning to FIG. 2, at block 206, the auto-selector can communicate which data-entry field was picked at block 204 to another application, such as guide application 112. In the illustrated example, the auto-selector communicates to the guide application that the meeting subject field is determined to be the data-entry field into which the handwriting should be entered. The guide application can indicate to a user that the meeting subject field is picked, such as by highlighting the field or presenting a handwriting guide in physical proximity to the field. These and other ways in which the guide application can use this information are set forth in greater detail below.

This process and the auto-selector enable a user to enter text into a field by handwriting alone, rather than having to select a data-entry field first before beginning to write. Also, as part of this process, the handwriting used to determine into which field the handwriting should be entered can itself be entered into that field; this is efficient because an action of a user is not wasted.

Exemplary Handwriting Guide

Referring to FIG. 5, an exemplary process 500 for presenting and generating a handwriting guide is shown. This process is illustrated as a series of blocks representing individual operations or acts performed by guide application 1112 and/or other components of architecture 100.

At block 502, the guide application receives location information. This information can comprise an indication of where on a screen handwriting is displayed, where handwriting has begun, an identity of a data-entry field, and/or a location of a data-entry field. In cases where the guide application receives an identity of a data-entry field, the guide application can analyze the screen and the data-entry form to determine where the data-entry field is located. In the illustrated example, the guide application receives from auto-selector 114 an indication that meeting subject field 404 (FIG. 4) is being written in by the user.

At block 504, the guide application determines, responsive to the location information, an orientation for a handwriting guide. If, for instance, the guide application receives an indication of where on a screen handwriting has begun, the guide application can orient the handwriting guide to encompass part or all of the handwriting.

If the guide application receives information indicating a data-entry field and a location where handwriting has begun, the guide application can present the handwriting guide based on the location information, the data-entry field, or both. The guide application, for instance, can receive location information indicating a selected data-entry field and entry of handwriting at a location not near the selected data-entry field. This can happen when a user selects a data-entry field with a gesture, like a tap, but then handwrites at some distance from the data-entry field. In this case the guide application can determine an orientation for the handwriting guide based on the writing instead of the data-entry field. This can be especially useful in cases where the handwriting guide is opaque because it permits a user to determine what part of a screen is obscured by where the user begins his or her handwriting.

In another embodiment, the guide application receives information indicating a data-entry field for entry of handwriting. Here the guide application can orient the handwriting guide based on the location of the data-entry field, whether or not handwriting has begun. The orientation for the handwriting guide can be geographically associated with the data-entry field, such as by being in physical proximity to, connected to, or superimposed over the data-entry field, for instance.

At block 506, the guide application presents a handwriting guide. The handwriting guide is a user interface indicating an area over which handwriting can be made and received. This user interface can guide a user's handwriting, such as by directing his or her size and angle of handwriting. In one embodiment the handwriting guide is presented as a solid, opaque window superimposed on the screen.

In another embodiment, the handwriting guide is presented having a lined border (e.g., a dashed-line box) that is otherwise substantially translucent. This translucence permits the user to view information previously viewable on the screen prior to the handwriting guide being presented. Thus, it does not substantially obscure context for the data-entry field or other features and information on the screen that is “under” the guide.

In still another embodiment, the handwriting guide is presented as a partially translucent area superimposed on the screen that shades the area occupied by the handwriting guide but permits the user to view substantially all features viewable on the screen prior to the handwriting guide being presented. By so doing, the handwriting guide leaves features and information on the screen substantially unobscured.

As an example, consider FIG. 6. There, the architecture presents a screen shot 600 of data-entry form 108 with an exemplary handwriting guide 602. In this ongoing, illustrated example, the guide application has received location information indicating that meeting subject field 404 (shown also in FIG. 4) is the field into which the handwriting should be entered. Responsive to this information, the guide application associates the handwriting guide to and orients it over the meeting subject field. This handwriting guide provides guidance to a user as to acceptable character size and angle at which to write, while also permitting the user to view context for the data-entry field by permitting substantially all of the information on the screen to be viewed (in this example the text “Meeting Subject:”).

Returning to FIG. 5, at block 508, the guide application receives handwriting indicia. This handwriting indicia can be in addition to the indicia already received and used as a basis for the orientation of the handwriting guide or can be indicia for the first handwriting received. The guide application can forward this handwriting indicia to ink recognition application 110, after which it can be converted to text and entered into an appropriate data-entry field. The guide application can forward this handwriting indicia after receiving an indication that a user is finished, such as with a command, or after a certain amount of time has passed. In addition, the guide application can alter the handwriting guide based on handwriting indicia received.

Continuing the ongoing illustrated example, FIG. 7 shows a screen shot 700 which is presented to the user. The screen shot shows the handwriting guide having an altered size from that shown in FIG. 6. In this example, the guide application receives additional handwriting indicia from a user indicating that the user is or may run out of room in the handwriting guide. Based on this information, the guide application expands the handwriting guide. Thus, when the user begins to write the word “and”, the guide application lengthens the handwriting guide. Likewise, when the user continues and writes the word “features”, the guide application adds a second line or increase the geometric footprint of the handwriting guide. Note that the handwriting guide does not substantially obscure the features of the screen, such as three data-entry fields and the following information: “Meeting Subject:”; “Meeting Organizer:”; “Start Date:”; “Start Time:”; and “5/7/2003”.

Returning to FIG. 5, at block 510, the architecture converts handwriting received in the writing guide into text and enters that text into the data-entry field. As an example, consider FIG. 8. There, the architecture presents a screen shot 800 showing text 802 in meeting subject field 404 that is a conversion of the handwriting written into the guide application and received as handwriting indicia at block 508. In this illustrated example, the handwriting enabled and received by the architecture and the guide application, “Tablet and Infopath features for version” is entered as text into the meeting subject field.

CONCLUSION

The above-described tools enable a user to write text into a data-entry field on a computing device's screen without independently selecting that data-entry field. These tools can also provide a handwriting guide capable of guiding a user's handwriting that is geographically associated with a data-entry field into which the user is intending to write and that permits substantially all features of a computing device's screen to be viewed. Although the invention has been described in language specific to structural features and/or methodological acts, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the claimed invention.

Claims

1. A method comprising: receiving handwriting made to a screen showing two or more data-entry fields, wherein at least a portion of the handwriting overlaps two or more data-entry fields; andentering text converted from the received handwriting into one of the data-entry fields without independently receiving a non-writing-based selection of that data-entry field.

2. The method of claim 1, wherein the act of receiving comprises receiving handwriting made over the screen with a stylus.

3. The method of claim 1, further comprising determining the data-entry field into which to enter the converted text using a bounding-type algorithm.

4. The method of claim 3, wherein the act of determining comprises determining a geographic relation between a first stroke or character of the received handwriting and the data-entry field.

5. The method of claim 1, further comprising presenting a handwriting guide in geographical association with the received handwriting.

6. The method of claim 5, wherein the handwriting guide both guides a user's handwriting and permits features that lie underneath the guide to be viewed by the user.

7. The method of claim 5, wherein the handwriting guide is capable of receiving additional handwriting made to the screen and guiding an angle and size of the additional handwriting while leaving features of the screen generally unobscured, and wherein the act of entering text comprises entering text converted from the additional handwriting into the data-entry field.

8. A computing device having a screen computer-readable media, and a processor capable of executing computer code stored on the computer-readable media, comprising of: Presenting one or more data-entry fields on the screen;Receiving handwriting made to the screen, wherein at least a portion of the handwriting overlaps two or more data-entry fields;Entering text converted from the handwriting into one of the data-entry fields without interaction independent of the handwriting received.

9. The device of claim 8 embodied as a hand-held computer.

10. The device of claim 8, wherein the screen comprises a tablet screen capable of receiving handwriting made over the tablet screen.

11. The device of claim 8, further capable of presenting a handwriting guide on the screen in geographical association with the selected data-entry field.

12. The device of claim 11, wherein the handwriting guide is capable of receiving additional handwriting made to the screen and guiding a size and angle of the additional handwriting while leaving features of the screen substantially unobscured.

13. The device of claim 8, further capable of selecting a data-entry field based on the location on the screen of the handwriting received and the data-entry field.

14. One or more computer-readable storage media having computer-executable instructions that, when executed, implement a method comprising: receiving handwriting made to a screen showing two or more data-entry fields, wherein at least a portion of the handwriting overlaps the two or more data-entry fields; andentering text converted from the received handwriting into one of the data-entry fields without independently receiving a non-writing-based selection of that data-entry field.

15. The one or more computer-readable storage media of claim 14, further comprising displaying a handwriting guide in geographical association with the received handwriting, wherein the handwriting guide is capable of permitting content of the data-entry fields and other features that lie 5 underneath the handwriting guide to be viewed.

16. The one or more computer-readable storage media of claim 15, wherein the handwriting guide is capable of guiding an angle and size of the user's handwriting.

17. The one or more computer-readable storage media of claim 15, wherein the handwriting guide is capable of receiving additional handwriting made to the screen and guiding an angle and size of the additional handwriting while leaving features of the screen generally unobscured.

18. The one or more computer-readable storage media of claim 14, wherein the screen comprises a tablet screen and the act of receiving comprises receiving handwriting made over the tablet screen.

19. The one or more computer-readable storage media of claim 14, further comprising selecting, responsive to the handwriting received, a data-entry field that is viewable on the screen.