RU2675152C2 - Quick tasks for on-screen keyboards - Google Patents

Abstract

FIELD: computing; counting.SUBSTANCE: invention relates to computer engineering. Method of changing text using a quick task includes monitoring text input in the user interface during interaction with the device via an on-screen keyboard, recognition, through the quick task module, the interaction scenario and automatic application, through the quick task module, of the quick task to change the text selected for the interaction scenario, wherein recognition based at least in part on the meaning of one or more words is achieved by parsing said one or more words to conclude about the intended meaning based on at least one of the combinations of words, the history of typical usage of words typical for the lexicon user.EFFECT: technical result consists in wider range of tools for the same purpose.20 cl, 8 dwg

Description

BACKGROUND

[0001] Computing devices, such as mobile phones, laptops and tablets, entertainment devices, handheld navigation devices, and the like, are generally implemented with on-screen keyboards (eg, functional keyboards) that can be used to enter text and / or other interconnection with computing devices. When a user enters or edits text characters in a text field or otherwise interacts with text using an on-screen keyboard, editing the input text can be difficult on some devices. For example, formatting text, inserting missing characters, and / or changing / translating an input text string on a mobile phone can be difficult due to the limited size of the device and on-screen keyboard. Although it is possible to provide predicted versions of text for a misspelled word, text prediction, as a rule, does not solve problems such as missed punctuation, character insertion, language translations, and so on. Thus, these text editing tasks require their resolution using traditional on-screen keyboards.

SUMMARY OF THE INVENTION

[0002] This application describes quick tasks for on-screen keyboards. In one or more implementations, the on-screen keyboard can support many quick tasks performed with the ability to edit selected text in a specific way. Shortcut functions can be assigned to on-screen keyboard keys in addition to the default actions or “normal” key character input functions. During text input (for example, when the cursor is active), the keys generally work to perform a function related to character input in order to enter the corresponding text characters. When text is selected, or while in other intended interaction scenarios, the operation of a key associated with a quick task can automatically launch a quick task to modify the selected text accordingly. Thus, the same on-screen keyboard key can be used to initiate a function related to character input, or to apply a quick task to the text depending on the interaction scenario.

[0003] This summary is provided in a simplified form for familiarizing yourself with selected ideas, which will be further described below in the detailed description of an embodiment of the invention. This description of the invention is not intended to identify key features or main features of the claimed invention, nor is it intended to be used as an aid in determining the scope of the claimed invention.

BRIEF DESCRIPTION OF THE DRAWINGS

[0004] A detailed description is described with reference to the accompanying drawings. In the drawings, the leftmost digit (s) of the reference number indicates the figure in which the reference number first appears. The use of the same reference numbers in various cases in the description and in the figures may indicate similar or identical objects.

[0005] FIG. 1 depicts an example work environment in which aspects of the fast task for on-screen keyboards can be implemented.

[0006] FIG. 2 depicts an example procedure in which a fast task is applied in accordance with one or more implementations.

[0007] FIG. 3 depicts an example of a procedure that is logic for determining when to apply fast tasks in accordance with one or more implementations.

[0008] FIG. 4 depicts an example quick task scenario in accordance with one or more embodiments.

[0009] FIG. 5 depicts various examples of quick tasks in accordance with one or more embodiments.

[0010] FIG. 6 depicts an example procedure in which many modifications associated with a quick task are presented for selected text in accordance with one or more implementations.

[0011] FIG. 7 depicts various examples of quick tasks associated with a variety of modifications in accordance with one or more implementations.

[0012] FIG. 8 depicts examples of systems and devices that can be used in one or more implementations of adaptive language models for text prediction.

DETAILED DESCRIPTION OF THE EMBODIMENTS

Overview

[0013] When a user enters text characters in a text field using an on-screen keyboard, editing the input text may be difficult on some small form factor devices. For example, formatting text, inserting missing characters, and / or changing / translating an input text string on a mobile phone can be difficult due to the limited size of the device and on-screen keyboard.

[0014] This application describes quick tasks for on-screen keyboards. In accordance with the described methods, the on-screen keyboard can support many quick tasks performed with the ability to edit the selected text in a specific way. Shortcut functions can be assigned to on-screen keyboard keys in addition to the default actions or “normal” key character input functions. During text input (for example, when the cursor is active), the keys generally work to perform a function related to character input in order to enter the corresponding text characters. When a text is selected or in other intended interaction scenarios, the operation of a key associated with a quick task can automatically launch a quick task to change the selected text accordingly. Thus, the same on-screen keyboard key can be used to initiate a function related to character input, or to apply a quick task to a text, depending on the interaction scenario.

[0015] In the following description, the “Work Environment” section describes an example environment that can be used in accordance with one or more implementations of quick tasks for on-screen keyboards. Next, a section entitled “Quick Task Details” describes the details and procedures of quick tasks in accordance with one or more embodiments. Finally, a section entitled “System Example” is provided that describes examples of systems and devices that can be used for one or more quick task implementations for on-screen keyboards.

Working environment

[0016] FIG. 1 shows an example of a system 100 in which quick task implementations for on-screen keyboards can be implemented. An example of a system 100 includes a computing device 102, which may be one or a combination of a fixed or mobile device, in any form of a consumer, computer, communication, portable, navigation, media playback, entertainment, gaming, tablet and / or electronic device. For example, computing device 102 may be implemented as a television client device 104, a computer 106, and / or a gaming system 108 that is connected to a display device 110 for displaying media content. Alternatively, the computing device may be any type of laptop computer, mobile phone, or portable device 112 that includes an integrated display 114. Any of the computing devices may be implemented using various components, such as, for example, one or more processing devices and storage devices as well as using any combination of the various components, as further described with reference to the example device of FIG. 8.

[0017] The integrated display 114 of computing device 112, or display device 110, may be a touch screen display that is configured to read touch inputs and gestures, such as, for example, a user-initiated character, key, typed, or selected input in a user interface that displayed on a touch screen display. Alternatively or additionally, examples of computing devices may include other variants of input mechanisms and devices, such as, for example, a keyboard, mouse, on-screen keyboard, remote control device, game control device, or any other type of device with user-initiated and / or user-selectable input .

[0018] In implementations, the computing device 102 may include an input module 116 that detects and / or recognizes touch input data 118 related to various types of input, such as, for example, character inputs from the on-screen keyboard, touch inputs and gestures, gestures camera-based inputs of the control device and other user-initiated inputs. Input module 116 is an example of functionality for identifying touch input and / or gestures and triggering operations to be performed corresponding to touch input and / or gestures. The input module 116, for example, may be configured to recognize a gesture detected by interacting with a touch screen display (for example, using touch screen functionality) of a user's hand. Additionally or alternatively, input module 116 may be configured to recognize a gesture detected by the camera, such as, for example, a wave of a user's hand, a capture gesture, hand position, or other specific gesture. Thus, touch inputs, gestures, or another input can also be recognized by touch input data 118 as including attributes (e.g., movement, selection point, position, speed, orientation, and so on) that are used to distinguish between different inputs, recognizable input module 116. This distinction can then serve as a basis for identifying a gesture from the inputs and, therefore, the operation to be performed based on the identification of the gesture.

[0019] The computing device includes a keyboard input module 120, which may be implemented as computer-executable instructions, such as software applications, or a module that is executed by one or more processing devices to implement the various implementations described herein. The keyboard input module 120 is a functionality for providing and controlling the on-screen keyboard for keyboard interactions with the computing device 102. The keyboard input module 120 may be configured to trigger a selective presentation of the on-screen keyboard representations at various points in time, such as when activating a text input field , search control or other text input control. An on-screen keyboard may be provided for display on an external display, such as a display device 110, or on an integrated display, such as an integrated display 114. Additionally, it should be noted that the Hardware-implemented keyboard / input device may also implement adaptable “ an on-screen ”keyboard having at least several function keys suitable for the methods described herein. For example, a hardware-implemented keyboard provided as an external device or integrated with computing device 102 may include a display device, touch keys, and / or a touch screen that can be used to perform quick tasks, as described herein. In this case, the keyboard input module 120 may be provided as a component of a device driver for a Hardware-implemented keyboard / input device.

[0020] The keyboard input module 120 may include or otherwise utilize a text prediction engine 122, which is a functionality for processing and interpreting symbol inputs 124 to generate and suggest predictions of suitable words corresponding to 124 symbol inputs. For example, an on-screen keyboard may be selectively presented in various interaction scenarios for entering text in a text input field, a password input field, search controls, generating data, a message thread, or other user interface text input control 126, such as, for example, a form, an HTML page, a UI application or document to facilitate user input of input characters 124 (e.g., letters, numbers, and / or other alphanumeric characters).

[0021] In general, the text prediction engine 122 determines one or more possible candidates that are most consistent with the input characters 124. Therefore, the text prediction engine 122 may facilitate text input by providing one or more predicted words that are set in response to user input 124 of characters. For example, words predicted by text prediction engine 122 can be used to perform auto-correction of input text, present one or more words as candidates for selection by a user to complete, change or correct input text, automatically change touch areas for on-screen keyboard keys, which match the predicted words, and so on.

[0022] In accordance with the methods described in this application, the keyboard input module 120 may be configured to include or use the quick task module 128, as described above and below. In general, the quick task module 128 is a functionality for supporting a plurality of quick tasks 130 for an on-screen keyboard. Quick tasks 130 are configured to facilitate editing operations that are usually difficult to perform using the on-screen keyboard. Types of editing operations for which appropriate quick tasks may be available include, but are not limited to, formatting, punctuation, insertion of characters, translations, and combinations thereof. Various non-limiting examples of quick tasks are described in relation to the following figures. A set of quick tasks 130, each of which is intended to perform a separate editing operation, can be assigned to the keys of the on-screen keyboard in addition to the character input functions or actions for the keys. The quick task module 128 may function to control the assignment of quick tasks to 130 keys, activate and deactivate quick tasks, create individualized quick tasks, and so on. Quick task module 128 can also work to recognize interaction scenarios associated with quick tasks (for example, text selections, cursor position, context, and so on), and apply suitable quick tasks to change the selected text when starting a quick task. The quick task module 128 may also implement logic to determine whether to execute the default function (for example, insert a text character) or perform the quick task assigned to the key responsible for the key operation. Additional details regarding these and other aspects of the on-screen keyboard quick tasks can be found in the following figures.

[0023] Having described an example work environment for fast tasks, now consider examples of methods and details that can be used in one or more of the implementations described in this application.

Quick Tasks Details

[0024] This section describes details of methods that apply quick tasks, with reference to examples of procedures in FIG. 2, 3 and 6 and examples of representations in FIG. 4, 5 and 7. In part of the following description, reference may be made to an example of the operating environment in FIG. 1, in which various aspects may be implemented. Aspects of each of the procedures described below may be implemented in hardware, firmware, or software, or a combination thereof. The procedures are depicted as a group of steps that define the operations performed by one or more devices and are not necessarily limited to the order depicted for the operations by the respective steps. In at least one embodiment, the procedures may be performed by a suitably executed computing device, such as, for example, the computing device 102 of FIG. 1, which includes or uses a module 128 quick tasks or comparable functionality.

[0025] FIG. 2 depicts a procedure 200 in which a fast task is applied in accordance with one or more implementations. Monitoring text input is carried out during interaction with the device via the on-screen keyboard (step 202). For example, text can be entered using the on-screen keyboard of a mobile device. Although aspects of an on-screen keyboard are described in this application, it must be understood that comparable ways to apply fast tasks can be accomplished using a hardware-implemented keyboard that has a touch keyboard, voice commands, or other input mechanism. A mobile phone or other computing device 102 may be configured to detect and process input to represent the entered text inside the user interface output on the device. Additionally, computing device 102 may use quick task module 128 to run quick tasks in appropriate circumstances. To do this, the quick task module 128 may be configured to monitor text input and keystrokes and make determinations as to when to initiate quick tasks depending on the interaction scenario.

[0026] More specifically, an input script is recognized that is configured to start a quick task assigned to an on-screen keyboard key associated with a character input function (step 204). Then, the quick task is used to change the text selected in relation to the interaction scenario, instead of performing the character input function associated with this key (step 206). As indicated, on-screen keyboard keys can be associated with character input functions as well as quick task functions. In response to the operation of a particular key, the quick task module 128 is configured to determine whether to perform “normal” character input functions or a quick task corresponding to a particular key. This definition may be based, at least in part, on recognition of the current interaction scenario. The interaction scenario, as used in this application, reflects the specific keystroke (or sequence of keystrokes) and the state or context of the interaction. The interaction scenario may be recognized in connection with the operation of a particular key. For example, pressing the “T” key of the on-screen keyboard when the cursor (for example, an insertion character) is active can cause the corresponding “t” character to be entered at the cursor location. On the other hand, if a text string is selected and then the T key is pressed, this particular interaction scenario may be associated with a quick task function, such as a quick translation task to translate a selected text automatically into different languages. Accordingly, the quick task module 128 recognizes the interaction scenario as associated with the fast task and initiates the quick task function associated with the “T” key to change the selected text string (for example, using translation) instead of inserting the “t” character. Thus, one way of recognizing interaction scenarios that trigger quick tasks is to determine whether the cursor is active or whether a text string is selected with respect to the key operation. In other words, the quick task module 128 can distinguish between different states for entering text, including at least the state of the active cursor corresponding to the character input functions and the state in which the text string associated with the quick tasks is selected.

[0027] In an implementation, quick task module 128 may also be configured to perform semantic processing of text that is entered and / or selected to inform a decision regarding whether to apply a quick task or whether to perform a character input function. Here, quick task module 128 may parse input text to conclude the intended value based on word combinations / probabilities, a library / history of typical word usage, a user vocabulary, and so on. If the quick task assigned to the current keystroke corresponds to the expected value extracted from the semantic processing, then the quick task module 130 recognizes this as the state in which to apply the quick task. Thus, the recognition of the interaction scenario as the launch of a quick task can additionally be based on all or part of the semantic processing of the text that is entered during interaction with the device.

[0028] It should be noted that the quick task module 128 is configured to apply at least some quick tasks based on a single key operation (eg, a single operation), as opposed to a key combination. Module 128 quick tasks automatically solves when the key is working, which of the many functions assigned to the key to perform depending on the interaction scenario. Each function can be triggered by a single key operation (for example, with a single keystroke). In this way, quick tasks can be implemented and applied without using keyboard shortcuts and / or modifier key combinations (for example, alt + A, ctrl + B and so on) used for some traditional keyboard shortcuts. Since the useful screen area may be limited for on-screen keyboards of mobile devices and key combinations may be difficult to execute on a small screen, the approach based on a single key operation used for quick tasks makes editing tasks easy for the user to perform and improves the overall user experience . Moreover, the on-screen keyboard can support a variety of quick tasks assigned to various keys, and can allow a user to change assignments and make user-defined assignments of predefined quick tasks to selected keys. The system may be further configured to facilitate the creation and assignment of individualized quick tasks to users.

[0029] FIG. 3 depicts a routine 300, which is logic for determining when to apply fast tasks, in accordance with one or more implementations. An operation of a key included in the on-screen keyboard is detected (step 302). This may occur based on monitoring text input, as described with respect to FIG. 2. In one approach, the quick task module 128 may implement logic to monitor each keystroke and control whether to perform normal action / symbol input or quick tasks assigned to the keys based on an interaction scenario. For example, suppose that a quick task, configured to format a selected text string by underlining text, is assigned to the “U” key. The quick task module 128 can detect when the "U" key is released or otherwise functions during a text input interaction, and decide whether to use the quick underline task or insert an alphanumeric character for the "U" key.

[0030] More specifically, the determination is made depending on whether a quick task is assigned to the key (step 304). For example, quick task module 128 may refer to a table or other suitable data structure that associates quick tasks with keys. In the above example, the quick task module 128 recognizes that the quick underline task is assigned to the “U” key. For some keys, quick task module 128 may determine that a fast task is not assigned and / or disabled for keys.

[0031] If a quick task is assigned to the key in step 304, then the interaction script is then analyzed to determine whether the interaction script is executed with the ability to run the quick task (step 306). When the interaction script launches the quick task, text editing operations corresponding to the quick task assigned to the key are initiated (step 308). On the other hand, the quick task module 128 may start operations for the intended key character input function (step 310) in response to determining that the fast task is not assigned to the key in step 304 and / or determining that the interaction script has not started the fast task on step 306.

[0032] For example, a quick task may be selectively started based on the current state of interaction. This can be based on whether the cursor is active or inactive for entering text or, alternatively, whether the user has selected the text. Contextual information regarding text input can also be used to determine how to respond to a keypress operation. In cases where the cursor is active, the key operation may lead to the input function of the intended character in the usual way. On the other hand, when the text is selected (for example, highlighted), quick tasks corresponding to the keys can be solved, and the key operation can then lead to the corresponding quick task instead of the character input function. In the above example, the operation of the “U” key may result in underlining the selected text when the text is selected before the key operation. On the other hand, in the normal text input mode with the active cursor, the operation of the “U” key can trigger operations to insert the corresponding alphanumeric character (for example, u or U in this example).

[0033] FIG. 4 depicts a quick task in accordance with an example interaction scenario, generally 400. More specifically, a user interface 126 is shown configured to interact with a text messaging application / service that has an on-screen keyboard 402 for a mobile phone device. The interface includes managing text input 404 in the form of a text message input field. In the illustrated example, the user interacts with the text input control 404 to input text characters “Que pasa, amigo” [ Spanish, “How are you, friend” ]. Additionally, the user interacts to select 406 text characters and, accordingly, the phrase “Que pasa, amigo” is presented as highlighted. In this scenario, selection 406 may be effective for activating quick tasks in accordance with the methods described in this application.

[0034] As shown in the example of FIG. 4, pressing 408 keys to select the “?” Key can lead to the execution of the assigned quick task 130, which inserts characters for Spanish questions before and after the selected phrase. Thus, modification 410 of the phrase “Que pasa, amigo” was made in response to pressing 408 keys to change the phrase “¿Que pasa, amigo?” [“How are you, friend?”]. Without a quick task, inserting characters before and after a phrase can be quite difficult and inefficient using the on-screen keyboard of a mobile device. Symbols of other foreign languages for punctuation are also expected to be comparable. Additionally, various types of quick tasks and individual fast tasks can be supported by an on-screen keyboard, some illustrative examples of which are depicted and described with respect to FIG. 5.

[0035] FIG. 5 depicts various examples of quick tasks that can be assigned to a total of 500 on-screen keyboards. For example, a quick punctuation task 502 is shown to automatically modify the punctuation of a selected phrase or line. Here, the quick punctuation task 502 corresponds to the example of FIG. 4, except that the quick task is presented as assigned to the “Q” key, and not to the “?” Key. Therefore, this example depicts that at least some quick tasks can be assigned to different keys, and, in some cases, the user may be able to set and change the binding of quick tasks to keys. In general, quick task 130 can be performed with the ability to perform punctuation operations to insert characters before and after a selected text phrase, one example of which is to insert question mark characters. Other quick punctuation tasks can be performed with the ability to help put the phrase in parentheses using the “)” or “(“, put the phrase in parentheses using the “[“, ”]”, “{“ or “}”, label html using the “>” or “<” key, inserting opening and closing exclamation points using the “!” key, etc. It should be noted that quick tasks can be assigned to many keys. For example, pressing keys or opening parentheses “( “Or closing the circle mated parentheses ")" can run the appropriate task for the rapid conclusion of the selected text in parentheses.

[0036] Additional quick tasks can be implemented to perform various types of formatting of the selected text. Quick formatting tasks can be performed with the ability to insert special characters (for example, time, currency and formatting social networks), switch the case of a word or sentence, switch the spelling of the text, switch between fonts, configure text effects, such as courses or bold , and so on.

[0037] For example, a quick time formatting task 504 for formatting suitable numbers in a text string as time values is also depicted in FIG. 5. In the illustrated example, a quick time formatting task 504 is assigned to the “:” key. Alternatively, the quick time formatting task 504 may be associated with and / or assigned by the user to another key, such as, for example, the “t” key, a fixed clock function key, or another selected key. When applicable, the quick time formatting task 504 can insert characters to format the time at appropriate positions within the text string. For example, the phrase “Game at 500” is depicted as being converted to “Game at 5:00” in response to applying the quick time formatting task 504. It should be noted that in this example, the initial phrase is not selected or highlighted, as in the previous example. This is intended to represent a situation in which the quick task module 128 can recognize and use the semantic context of the interaction script and automatically apply the fast task. Thus, the user may not make an explicit choice of text to use some quick tasks. Here, for example, the quick task module 128 may assume that the user meant “at 500” as an indication of time. Accordingly, when the “:” key is functioning, the quick time formatting task 504 is automatically applied instead of inserting the “:” at the displayed cursor location.

[0038] The italics fast task 506 is depicted as another example of a fast formatting task that may be supported. Here, selecting the text followed by the operation of the “i” key causes the selected text to switch to the font in italics. In an implementation, the operation “i” may again cause the selected text to return back to the font in italics. In general, quick tasks, as described in this application, allow the user to cycle through and switch back and forth between the text as input (for example, the original text and formats), and one or more modifications of the text available using the quick tasks, by sequentially function key to which a quick task is assigned. Examples with regard to fast tasks performed with the ability to cycle through many different modifications are described further with respect to FIG. 6 and 7.

[0039] Quick tasks for performing a variety of formatting actions, comparable to the examples just described, can be defined and assigned to various selected keys. Some additional examples of quick formatting tasks that can be assigned to specific keys include, but are not limited to “b” for bold text, “c” or “shift” to switch case / lower case for a word, phrase, or choice, “f” to change to another font, “u” to underline, and so on.

[0040] Another example includes automatic tag formatting, which can be used for social networks or other purposes. One type of tagging is the use of the phrase “#” for posts on social networks. This type of labeling can be used not only for social networking services, but also in email, text messaging and other types of communication. FIG. 5 is a quick social formatting task 508 that can be assigned to the “#" key. In operation, a quick social formatting task 508 functions to convert a phrase into a label in a targeted format. In the example depicted, the phrase “Aaron Rogers MVP” entered is converted by a quick task to “# Aaron Rogers MVP”. Here the pointer for the “#” mark was inserted at the beginning of the entered phrase, and the spaces were removed. Other types of labels that use different pointers and even user-defined formatting operations can be accomplished using quick tasks.

[0041] FIG. 5 further represents a quick translation task 510, which can be assigned to the “t” key, as shown, a language keyboard key or other key. Quick translation task 510 can be applied to translate a phrase or selected text from one language to another. Here, the phrase “Where is the hotel?” Can be automatically translated from English into another designated language, such as the Spanish version “¿Donde está el hotel?” Translation can be done by selecting the text and pressing the “t” key or another key, related to the fast task 510 translation. The user can customize a specific language for use in translations. Additionally or alternatively, the fast translation task 510 may be configured to cycle through an ordered list of a plurality of languages, the details of which are described with respect to the following figures.

[0042] FIG. 6 depicts a procedure 600 in which many modifications associated with quick tasks can be applied. A quick task that involves many modifications for applying the selected text is assigned to a screen key (block 602). A key operation has been detected to initiate a quick task (step 604). Then, many modifications of the selected text are presented in response to a subsequent key operation (step 606).

[0043] As mentioned, an on-screen keyboard that includes or uses a quick task module 128 may support some quick tasks that carry out many modifications. In one approach, a plurality of modifications are defined according to a list or data structure that indicates the order for applying the modifications. For example, a list of languages for translations can be associated with a quick translation task, a list of available fonts can be used for a quick font selection task, and a quick time formatting task can include various available time formats. Other quick tasks may function to switch back and forth between unchanged text entered and a specific text modification. When a key associated with a quick task that provides many different modifications is selected multiple times, the system can cycle through the list of modifications one after the other and modify the corresponding text to appear on the user interface in succession in response to the sequential key operation. Thus, every time you press a key, an excellent modification appears in accordance with going through the list of available modifications for a quick task. When each modification in the list has been presented, the next selection of a particular key may cause the selected text to return to its unmodified form.

[0044] For further illustration, FIG. 7 depicts a total of 700 examples of scenarios in which fast tasks are applied that carry out many modifications. For example, the quick translation task 702 is depicted as being associated with the “k” key. The quick translation task 702 in this example is associated with a list of 704 languages. A list of 704 languages is data associated with a quick task, which is sufficient to define and / or manage a variety of text modifications and to identify the order in which the modification is applied to the quick task. Here, a list of 704 languages indicates consecutive translations into Spanish, French, German and then back to the default language (in this case, English). After successive keystrokes of the “x” key, the quick task module 128 can function to cycle through the list of languages 704 and apply the corresponding translations to different languages, as shown in 706. The user can scroll one or more possible modifications sequentially by pressing the key again and can select one from modifications for keeping an explicit choice, additional text input and / or after the expiration of the inactivity period.

[0045] A comparable example of the fast time formatting task 708, which supports many modifications, is also shown in FIG. 7. In this scenario, the quick time formatting task 708 is presented as associated with the “t” key. Fast time formatting task 708 can also be assigned to the “:” key, just like quick time formatting task 504, described with respect to FIG. 5. The quick time formatting task 708 in this example is associated with a list of 710 time formats. A list 710 of time formats indicates consecutive modifications of the time format for the associated text. After successively pressing the “t” key, the quick task module 128 can function to cycle through the list of 710 time formats and apply the corresponding modifications, as shown in 712. Accordingly, the “500” part of the text can change to “at 5:00”, “At 17:00” and back “at 500” in response to successive presses of the “t” key.

[0046] In general, keyboard shortcut assignments can be predefined for the on-screen keyboard. In an implementation, appointments can also be made by the user to make individual appointments. Thus, the user can select the destination of the quick translation task to the “x” key and the quick time format task to the “t” key, as shown in FIG. 7 rather than predetermined assignments, such as using “t” for translation and “:” for time, as in FIG. 5. The quick task module 128, for example, can present an interface by which a user can interact with a binding that binds the various available quick tasks to keys. Using the interface, the user can change predetermined appointments and / or can enable or disable fast tasks, in general or on an individual basis. Additionally, the interface and fast task binding can be configured to allow users to create an individualized fast task using the quick task creation dialog. The creation dialog may facilitate the selection of individualized character inserts, formatting and / or launching quick tasks using appropriate syntax, menus, fields and labels, and so on. An individualized quick task can be determined according to the user's choices made through the quick task creation dialog. An individualized quick task can be assigned to a key of your choice. For example, but not limitation, the user can define a quick combination task for bold, italics and underscores, which converts the selected text string into a modified string with bold, italics and underscores. The user can assign this individualized quick task to a key, such as the “z” key. In another example, an individualized quick task may be created to facilitate the insertion of selected special characters at specific locations within the text string. For example, the quick task of an asterisk sign can be defined to enclose text inside asterisks, such as changing “Hello Robin” to “*** Hello Robin ***”. Various other types of individualized and predefined quick tasks are also contemplated.

[0047] Having described some exemplary details and methods related to quick tasks, we now consider an example of a system that can be used in one or more of the implementations described in this application.

System and device example

[0048] FIG. 8 depicts an example system 800 that includes an example computing device 802, which is one or more computing systems and / or devices that can implement the various methods described herein. Computing device 802, for example, may be a service provider's server, a device associated with a client (eg, a client device), a chip system and / or any other suitable computing device or computing system.

[0049] An example computing device 802, as shown, includes a processing system 804, one or more computer-readable media 806, and one or more I / O interfaces 808 that are connected in communication with each other. Although not shown, computing device 802 may further include a system bus or other data and an instruction transfer system that connects the various components to each other. A system bus may include any or a combination of various bus structures, such as, for example, a storage bus or memory control device, a peripheral bus, a universal serial bus and / or a processing bus or a local bus that uses any of a variety of bus architectures. Other diverse examples are also contemplated, such as control and data lines.

[0050] The processing system 804 is a functionality for performing one or more operations using hardware. Accordingly, the processing system 804 is depicted as including Hardware-implemented elements 810 that can be implemented as processing devices, functional blocks, and so on. This may include the implementation in technical means as a specialized custom integrated circuit or other logic device formed using one or more semiconductors. Hardware implemented elements 810 are not limited to the materials from which they are formed, or to the processing mechanisms used in them. For example, processing devices may consist of semiconductor (s) and / or transistors (e.g., electronic integrated circuits (ICs)). In such a context, the instructions executed by the processing device may be electronically executable instructions.

[0051] Computer-readable media 806 is depicted as including a storage device / storage 812. Storage device / storage 812 is the capacity of a storage device / storage associated with one or more computer-readable media. Storage device / storage 812 may include volatile media (such as random access memory (RAM)) and / or non-volatile media (such as read only memory (ROM), flash memory, optical disks, magnetic disks and so on). Storage device / storage 812 may include fixed media (e.g., RAM, ROM, fixed hard disk, and so on), as well as removable media (e.g., flash memory device, removable hard disk, optical disk, and so on). Computer-readable media 806 can be implemented in many other ways, as further described below.

[0052] The I / O interface (s) 808 are functionality to allow a user to enter commands and information into computing device 802, and also allow the presentation of information to the user and / or other components or devices using various input / output devices. Examples of input devices include a keyboard, a cursor control device (e.g., a mouse), a microphone for voice operations, a scanner, touch functionality (e.g., capacitive or other sensors that are capable of detecting a physical touch), a camera (e.g., which can use visible or invisible wavelengths, such as infrared frequencies to detect movement that does not involve touching as gestures) and so on. Examples of output devices include a display device (e.g., a monitor or projector), speakers, a printer, a touch response device, and so on. Computing device 802 may further include various components to enable wired and wireless communications, including, for example, a network interface card for network communications and / or various antennas to support wireless and / or mobile communications. Many different types of suitable antennas are contemplated, including but not limited to one or more Wi-Fi antennas, global navigation satellite system (GNSS) or global positioning system (GPS) antennas, cellular antennas, near field communications antennas 214 (NFC), antennas Bluetooth and / or so on. Thus, computing device 802 can be performed in a variety of ways, as further described below, to support user interaction.

[0053] Various methods may be described herein in the general context of software, hardware-implemented items, or software modules. In general, such modules include standard programs, programs, objects, elements, components, data structures, and so on, that perform specific tasks or implement specific abstract data types. The terms “module”, “functionality” and “component”, as used herein, are generally software, firmware, hardware, or a combination thereof. The features of the methods described in this application are platform independent, which means that the methods can be implemented on a variety of commercial computing platforms having multiple processing devices.

[0054] The implementation of the described modules and methods may be stored or transmitted on some form of computer-readable media. Computer-readable media may include a variety of media that computing device 802 can access. By way of example, but not limitation, computer-readable media may include “computer-readable media” and “communication media”.

[0055] “Computer-readable storage media” refers to media and / or devices that allow information to be stored, compared to conventional signal transmission, carrier waves or the signals themselves. Thus, computer-readable storage media include technical means, such as volatile and non-volatile, removable and non-removable media and / or storage devices implemented by a method or technology suitable for storing information, such as computer-readable instructions, structures data, program modules, logic elements / circuits, or other data. Examples of computer-readable storage media may include, but are not limited to, RAM, ROM, EEPROM, flash memory devices or other memory technology, CD-ROMs, digital versatile disks (DVDs) or other optical storage devices, hard drives, magnetic tapes, magnetic tape, magnetic disk storage or other magnetic storage devices, or other storage devices, tangible media or articles suitable for storing the desired information, and which can be accessed by a computer.

[0056] “Communication media” refers to signal carriers, configured to transmit commands to hardware of computing device 802, such as over a network. Communication media can typically embody computer-readable instructions, data structures, program modules or other data in a modulated data signal, such as carrier waves, data signals, or another transmission mechanism. Communication tools also include any information delivery media. The term “modulated data signal” means a signal that has one or more characteristics configured or changed in such a way as to encode information in the signal. By way of example, but not limitation, communication media includes wired media, such as a wired network or a direct wired connection, and wireless media, such as acoustic, RF, infrared, and other wireless media.

[0057] As described above, the hardware-implemented elements 810 and computer-readable media 806 are commands, modules, programmable device logic and / or fixed device logic implemented in the form of hardware that can be used in some implementations to implement at least some aspects of the methods described in this application. Hardware-implemented tools can include components of an integrated circuit or systems on crystals, specialized custom integrated circuits (ASICs), a user-programmable gate array (FPGA), a complex device (CPLD) with programmable logic, and other implementations in semiconductor or other hardware-implemented devices. In this context, a Hardware-implemented element may function as a processing device that performs program tasks defined by instructions, modules and / or logic embodied by this Hardware-implemented element, as well as a Hardware-implemented device used to store instructions for execution, for example, computer-readable media described previously.

[0058] Combinations of the above can also be used to implement the various methods and modules described herein. Accordingly, software, hardware, or software modules including a text prediction engine 122, quick task module 128, and other software modules may be implemented as one or more instructions and / or logic embodied in some form of computer-readable storage media and / or one or more Hardware-implemented elements 810. Computing device 802 may be configured to implement specific commands and / or functions corresponding to software th firmware and / or hardware modules. Accordingly, the implementation of modules as a module, which is executed by computing device 802 as software, can be achieved, at least in part, by technical means, for example, by using computer-readable storage media and / or Hardware-implemented elements 810 processing systems. Commands and / or functions may be performed / operated using one or more products (eg, one or more computing devices 802 and / or processing systems 804) to implement the methods, modules, and examples described herein.

[0059] As further illustrated in FIG. 8, an example system 800 provides a unified environment for a seamless user experience when running applications on a personal computer (PC), television device, and / or mobile device. Services and applications run essentially the same in all three environments for the same user experience, when moving from one device to the next while using the application, playing a video game, watching a video, and so on.

[0060] In an example system 800, a plurality of devices are interconnected by a central computing device. A central computing device may be local to multiple devices or may be located remotely from multiple devices. In one embodiment, the central computing device may be a cloud of one or more server computers that are connected to multiple devices over a network, the Internet, or another data link.

[0061] In one implementation, this interconnection architecture allows the delivery of functionality to multiple devices to provide a common and seamless experience to the user of the multiple devices. Each of the many devices can have different physical requirements and abilities, and the central computing device uses a platform to allow the delivery of experience to a device that is also specially configured for the device while being common to all devices. In one implementation, a class of target devices is created, and experiments are specifically tuned for a universal class of devices. A class of devices can be defined by physical attributes, types of use, or other general characteristics of the devices.

[0062] In various implementations, computing device 802 may assume many different configurations, such as for computer 814, mobile 816, and television 818 use. Each of these configurations includes devices that may have a generally different design and capabilities, and thus computing device 802 may be configured in accordance with one or more of various classes of devices. For example, computing device 802 may be implemented as a computer class 814 of a device that includes a personal computer, a desktop computer, a multi-screen computer, a laptop computer, a netbook, and so on.

[0063] Computing device 802 may also be implemented as a mobile device class 816, which includes mobile devices such as a mobile phone, portable music player, portable gaming device, tablet computer, multi-screen computer, and so on. Computing device 802 may also be implemented as a television device class 818, which includes devices having or connected, typically with larger screens, under normal viewing conditions. These devices include televisions, set-top boxes, game consoles, and so on.

[0064] The methods described herein can be supported using these various configurations of computing device 802, and are not limited to specific examples of the methods described in this application. This is illustrated by including the quick task module 128 in the computing device 802. The functionality of the quick task module 128 and other modules can also be implemented in whole or in part by using a distributed system, such as, for example, on the “cloud” 820 on the platform 822, as described below .

[0065] The cloud 820 includes and / or is a platform 822 for resources 824. A platform 822 abstracts the basic functionality of hardware (eg, servers) and software resources of the cloud 820. Resources 824 may include applications and / or data, which can be used when computer processing is performed on servers remote from computing device 802. Resources 824 may also include services provided over the Internet and / or over a subscriber network, such as, for example, a cellular or Wi-Fi network .

[0066] Platform 822 may abstract resources and functions for connecting computing device 802 to other computing devices. Platform 822 can also serve to abstract resource scaling to provide an appropriate level of scale for the detected demand for resources 824, which are implemented on platform 822. Accordingly, in the implementation of the connected device, the implementation of the functionality described herein can be distributed across system 800. For example, functionality may be implemented in part on computing device 802, as well as on platform 822, which abstracts the functionality of cloud 820.

Conclusion

[0067] Although the methods in the foregoing description of an embodiment of the invention are described in a language specific to structural features and / or methodological actions, it should be understood that the invention in the appended claims is not necessarily limited to the specific features or actions described. On the contrary, specific features and actions are disclosed as examples of embodiments of the claimed invention .

Claims (43)

1. A method for changing text using a quick task, comprising: monitoring text input in the user interface during interaction with the device via the on-screen keyboard displayed in said user interface; recognizing, by means of the quick task module, an interaction script configured to launch a quick task assigned to a key associated with an on-screen keyboard character input function, the recognition being based at least in part on the value of one or more words that are entered during interaction with device and automatic application, through the quick tasks module, of a quick task to change the text selected in relation to the interaction scenario, instead of performing the character input function associated with the said key, however, recognition based, at least in part, on the meaning of one or more words is achieved by parsing said one or more words to conclude on the intended meaning based on at least one of the combinations of words, a history of typical use of words specific to the user of the lexicon . 2. The method according to claim 1, wherein the on-screen keyboard is configured to support a variety of quick tasks assigned to the various keys of the on-screen keyboard. 3. The method according to claim 1, in which the recognition of the interaction scenario, configured to run a quick task, further comprises determining a state for entering text in which a text string is selected. 4. The method of claim 1, wherein the fast task is applied in response to a single key operation. 5. The method of claim 4, wherein the plurality of functions assigned to the key, including the quick task and the character input function, are executed by a single key operation depending on the interaction scenario. 6. The method according to claim 1, wherein the character input function is started to cause the text character corresponding to the key to be inserted when the cursor is active for entering text, and the quick task is started when the cursor is inactive for text input in response to recognition of an interaction scenario. 7. The method according to claim 1, in which the quick task is performed with the ability to contribute text editing functions to change the selected text, including one or more of: formatting the selected text, punctuation for the selected text, inserting a character in relation to the selected text or translation selected text. 8. The method according to claim 1, further comprising: assigning a quick task to a key in accordance with a user selected quick task assignment to a key. 9. The method according to claim 1, additionally containing: showing an interface to enable the creation of a quick task as an individualized quick task using the dialog for creating quick tasks; and defining a quick task in accordance with the user's choices made through the quick task creation dialog. 10. A computing device containing: processing system; and one or more computer-readable media storing instructions that, when executed by the processing system, carry out: an on-screen keyboard user interface for a computing device having a plurality of keys, each of which is associated with a default character input function; and quick tasks module, configured to: assign two or more quick tasks performed with the ability to contribute text editing functions to a variety of keys; recognize the operation of a particular key; determine an interaction scenario in connection with the operation of said specific key; in response to the determination that the interaction scenario is the first interaction scenario, call the execution of a character input function associated with said specific key; and in response to the determination that the interaction scenario is the second interaction scenario, cause the execution of a quick task from the two or more quick tasks assigned to said specific key, the quick task being configured to automatically reformat the text according to the social network format in response to the operation of the said specific key . 11. The computing device of claim 10, in which: the character input function for a particular key is executed when the first interaction scenario corresponds to a state in which the cursor for entering text is active. 12. The computing device of claim 10, in which: the quick task for a particular key is executed when the second interaction scenario corresponds to the state in which the user selected a test line. 13. The computing device of claim 10, wherein the quick tasks assigned to the plurality of keys include a quick task for invoking translation of a selected text between languages. 14. The computing device of claim 10, wherein the quick tasks assigned to the plurality of keys include one or more quick formatting tasks to facilitate inserting special characters, switching case, word spelling, switching between fonts, or setting text effects to relative to the selected text. 15. The computing device of claim 10, wherein the quick tasks assigned to the plurality of keys include one or more quick punctuation marks tasks configured to perform punctuation marks to insert characters before and after the selected text. 16. The computing device of claim 10, wherein at least one of the quick tasks assigned to the corresponding key is associated with several changes, and the actuation of the corresponding key is configured several times with the ability to cycle through these several changes to apply these several changes to the selected text one by one. 17. A method for changing text using a quick task implemented by a client computing device, the method comprising: assigning a quick task to one key out of the numerous keys of the on-screen keyboard of the user interface displayed by the display of the client computing device, the quick task being associated with several changes to be applied to the selected text, the quick task being configured to facilitate text editing functions to change the selected text by translating the selected text into one or more assigned languages, with several changes defined according to the data structure, defining th order in which the change should be applied to the selected text; detecting the operation of said one key using the on-screen keyboard to initiate a quick task; and presentation on the display of the client computing device of the aforementioned several changes of the selected text in response to the next operation of the mentioned one key by cycling through the data structure in order and automatically causing the appearance of the corresponding changes applied to the corresponding text in the user interface, one after the other according to the order of the corresponding changes in the structure data, and these few changes are configured for translation by the client computing device stvom selected text in two or more additional languages in response to the regular operation of the same one key, the data structure defines an ordered list of languages for translating the selected text. 18. The method of claim 17, wherein the quick task is configured to facilitate text editing functions for changing the selected text, the text editing functions including one or more of: formatting the selected text, punctuation for the selected text, inserting a character in relation selected text or translation of selected text. 19. The method according to 17, in which cyclic passage in order of the data structure further comprises returning the selected text to an unchanged form in response to presenting each change of the aforementioned several changes in the data structure and receiving an additional operation of said one key. 20. The method according to 17, further comprising: showing the user interface on the display of the client computing device; and receiving input from the user to change the assignment of a quick task from said one key to another one key from the mentioned numerous keys.

Images