User-machine interface

[0001] User-machine interface has made great strides with the introduction of icons displayed on a screen and a mouse manipulating a pointer. As is well known, icons may be “grabbed” by pointing a mouse, click and hold, and moving the icon anywhere on a screen. For example, if the icon is moved into a “shredder” icon, the icon or the document represented by the icon may be deleted.

[0002] A user-machine interface is disclosed that relies on the use of a line, having a start and an end, that connects various objects displayed on a screen. The line may start at a source object, extend to intersect other objects, and end at some desired location on the screen. A location of the start of the line may identify a specific portion of the source object as a source. If the line extends to intersect a command object, then the source may be used as input to a command corresponding to the command object for processing. If the line ends at a sink object, the processed source may be placed at a location indicated by the end of the line. If the end of the line cannot be associated with an object, then the processed data may simply be displayed at a location of the end of the line, for example.

[0003] The line may include various line shapes. For example, if the line starts by substantially surrounding a portion of the source object, that portion surrounded by the line is identified as the source to be processed by later commands. The line shape at the start of the line may also imply commands that should be performed on the source. For example, if the start crosses out a word of the source object in a particular direction such as from right to left, this line shape may command cutting the word from the source object.

[0004] The line may extend into a line shape that does not intersect with any object. Such line shapes may be interpreted as commands. For example, a simple loop may indicate the “insert” command, for example. Thus, if the line starts with a straight line crossing out a word in a source object, extends into a loop, and ends at a particular point in a sink object, then the word in the source object may be cut and inserted at a location indicated by the end of the line.

[0005] Objects may be one or more sources, sinks or commands. Command icons may be simply a line (a command bar) drawn across the screen, to separate the screen into two portions, for example. A line drawn starting from one portion of the screen, crossing the command bar into another portion of the screen may indicated copying (or cutting) text from the first portion of the screen into the second portion of the screen, for example. Source and sink objects may be of any kind and not limited to text. For example, source and sink objects may be network related such as email addresses, cell phone numbers, TV or radio stations, for example. Further, commands may also be non-text related such as voice synthesizers, video displays, headphones, etc.

[0006] In view of the above, instead of entering commands via keyboard or using a mouse, drawing of a substantially contiguous line to form various shapes and intersecting various objects provides an intuitive and simple method for communicating with a machine. Such a user-machine interface may be easily adaptable to any type of devices including xerographic devices such as copiers or printers with display command entry areas, hand-held units such as PDAs, cell phones, etc.

[0026] FIG. 1 shows an exemplary display screen 100 that displays objects 102-110. For this example, objects 102-106 are source/sink objects and objects 108 and 110 are command objects. Source/sink objects 102-106 may represent documents/files/ports/network connection, etc., to or from which data may be input and/or output. Command objects 108-110 may represent actions that may be performed relative to source/sink objects 102-106 or data within them.

[0027] For example, FIG. 2 shows a substantially contiguous line 116 that begins at object 102, intersects object 108 and ends at object 106. The substantially contiguous line 116 may be formed by ordinary means such as a pointer or a stylus using a touch sensitive screen, for example. These and other methods for forming a line may involve small gaps in the line. In any case, any gaps in the line must be of a small enough magnitude for the appropriate technology to distinguish one line from multiple lines. A dashed circle 112 is used to identify the start of line 116, and a double dashed circle 114 is used to identify the end of line 116. The dashed circle and double dashed circle 112 or 114 may not be actually displayed but are used here to indicate starts and ends of lines. The intersection of line 116 with object 108 may be crossing object 108 as shown in FIG. 2, or parameters may be set so that line 116 may only need to come within a certain set distance of object 108 to be interpreted as intending to include object 108.

[0028] Line 116 represents a command to direct a machine to perform a function as represented by object 108 using object 102 or a portion of object 102 as input and placing the output in object 106. Thus, instead of using a pointer and a mouse, for example, to select object 102, and dragging object 102 to object 108 for a function to be performed, line 116 is actually drawn as a visible entity that connects source/sink objects with command objects.

[0029] FIG. 3 shows another example where a line 118 includes a line shape 120 at the source end and connects two command objects 108 and 110 before reaching the sink object 102. As shown in FIG. 3, line shape 120 may have a substantially closed perimeter surrounding a portion of object 104 to identify the source. It is immaterial whether the closed perimeter is completely closed. The purpose of the substantially closed perimeter is to unambiguously identify the source. Any shape sufficient for performing the identification function is acceptable.

[0030] The functions to be performed on the identified source is a combination of two functions as represented by command objects 108 and 110. The results after performing functions associated with command objects 108 and 110 may be placed in the object 102 at a location identified by the end of line 118. The commands 108 and 110 may be performed in the order from source to sink along line 118. Other order schemes may be constructed such as resolving order based on types of command objects included by line 118.

[0031] FIG. 4 shows another example in which line 122 includes line shapes 124, 126 and 128. Similar to line shape 120, line shape 124 may identify a source data, and, additionally, specify a function such as copy or cut, for example. Line 122 does not cross a command object relative to the source. Instead, line shape 126 is included and may be interpreted to be with a predefined function. Further, line shape 128 specifies not only a location where the processed results should be placed, but also a specific space within which the process results should fit by adjusting text reflow, size, etc., for example. Thus, using line shapes 124, 126, and 128, the data in object 104 may be identified and processed via the function identified by line shape 124 and line shape 126, and the result placed in object 102 at the location identified by line shape 128. Multiple line shapes may also be included to specify additional commands. For example, if the source data is to be copied, put into bold font with underline, then two different line shapes, one for bold and one for underline, may be used instead of the one line shape 126.

[0032] FIG. 5 shows an example display screen 200 that includes a display section 204, a command bar 206 and a display section 208. Display sections 204 and 208 may be touch sensitive, for example, to facilitate use of a stylus. Other ways of drawing a line and line shapes are well known, such as, for example, using a mouse or keys of a keyboard other than touch sensitive screens. The command bar 206 is a type of command object and a command is “entered” by extending a line to cross command bar 206. FIG. 5 may represent an example in which a user may be reviewing documents 210-214 using a PDA or cell phone, for example, and decides to enter an ink comment 222 such as “good concept.” Then, the user may want to place the comment at a particular location of document 210. Thus, as shown in FIG. 6, the user may use a stylus to draw line 224 starting at ink comment 222 and ending at a position that ink 222 comment should be placed in document 210. Upon receiving line 224, a command processor may cut ink comment 222, size it based on the display size of document 210 and place the sized ink comment at the location indicated by the end of line 224 as shown in FIG. 7.

[0033] FIG. 8 shows a line shape 216 at the end of line 218 that indicates how to place ink comment 222. FIG. 9 shows another example in which line 220 starts at ink comment 222 and ends in a substantially closed perimeter line shape 226 to specify where and how ink comment 222 is to be placed. As shown, ink comment 222 is reflowed and sized to fit into space substantially encompassed by line shape 226. FIG. 10 shows yet another example of a line shape 230 that identifies the word “example” as source data to be copied to a position below ink comment 222. In this case, line shape 230 is interpreted as a “copy”. The command processor could be set to interpret line shape 230 as a “cut” if it crosses the word “example” from left to right instead of right to left, for example. FIG. 11 shows an example of a substantially closed perimeter line shape 232 that encompasses a graph in document 214 and making a copy (or moving it) to display section 208 via line 234.

[0034] FIG. 12 shows a command bar 306 that includes fields 308-314. Each of fields 308-314 may be defined to represent possible functions that may be either predetermined or set by the user directly or set using a profile, for example. While FIG. 11 identifies fields 308-314 as labeled rectangles, these fields may be identified via color, icon or other convenient and meaningful symbols familiar to the user.

[0035] In FIG. 13, a line 304 starts at ink comment 222, intersects fields 310 and 314 and ends at document 212. Fields 310 and 314 may identify other accessible machines to which ink comment 222 may be transmitted. For example, fields 310-314 may represent colleagues of the user. Thus, the user forming line 304 transmits ink comment 222 to colleagues corresponding to fields 310 and 314 to communicate the approval. Colleagues corresponding to fields 308 and 312 do not receive ink command 222, even if viewing document 212. If colleagues corresponding to fields 310 and 314 are also viewing document 213, then the ink comment may be placed in the colleagues copy of document 212 at the location indicated by the user.

[0036] While examples shown in FIG. 5-FIG. 13 show ink comment 222 in display section 208, other types of objects may be placed there. For example, FIG. 14 shows email 402 as a source object, and line 404 starting at email 402, and ending at a desired location in display section 204. Line 404 crossing command bar 206 may be interpreted as a command to receive email 402 and display its contents as a document 213 in display section 204. FIG. 15 shows an example in which the user may place line 406 starting at document 215 and ending at sink object 408. Sink object 408 may be a “send” object that may be initialized to send email and/or facsimile via a network connection, for example, to addresses listed in an associated address file. Thus, line 406 may correspond to a command to send document 215 as email to addresses indicated in the address file. Additionally, FIG. 15 shows another line 412 that starts at ink comment 414 and ends at sink object 410 that may represent an instant message session. Thus, line 412 commands sending ink comment 414 to instant message(s) partner associated with object 410. The instant message session may automatically display message inputs so that the user need not explicitly “receive instant messages.

[0037] FIG. 16 shows command bar 206 replaced by command bar 306, and email 402 is opened and displayed in display section 204. Field 308 may represent “self” or “personal” and the email is not sent to any other party. Other network type communications may also be possible such as receiving or sending audio files, video clips, TV or radio stations, Internet connections or communications with cell phones via text-to-voice or voice-to-text, etc.

[0038] As discussed in connection with FIGS. 1-4, command objects may be in any shape and not limited to command bars 206 and 306 as discussed in connection with FIGS. 5-16. For example, FIG. 17 shows command objects 506 and 508 in shapes of familiar icons. Command object 506 may be a voice synthesis icon that performs text-to-voice conversion to enunciate text. Command object 508 may be a magnifier command that displays, in magnified fashion, the selected text.

[0039] As shown in FIG. 17, line 504 includes line shape 502 that identifies a particular paragraph in document 212. Line 504 may end at command object 506. In this case, the machine inputs the selected text into a voice synthesizer and generates audio output to “read” the selected text. If the user further extends line 504 with line portion 510 shown as a dashed line to end at command object 508, the selected text may be also displayed in portion 512 of display screen 200, for example, and the word currently enunciated may be highlighted as shown by highlight 514. In this way, a user of a hand-held unit with limited display space and resolution may have a portion of a displayed document read audibly and, if desired, the portion of the document may be displayed for confirmation. A headphone icon may be used if audio is output to a headphone for privacy.

[0040] FIG. 18 shows an exemplary block diagram of a machine 600 that may perform the functions in connection with entering commands via lines as discussed above. Machine 600 may include a command processor 602, a memory 604, a line shape discriminator 606, a command discriminator 608, an input/output controller 610, a display controller 612 and a network interface 614. These components 602-614 may be coupled together via one or more buses 616.

[0041] While FIG. 17 shows machine 600 configured in a bus architecture format, other architectures may be used as is well known to one of ordinary skill. Additionally, while separate blocks are used to illustrate various functional units, these blocks may be combined or further divided based on available technology. Hardware implementation such as application specific integrated circuits (ASCIs) or software implementations using either general or application specific processors such as DSPs may be used.

[0042] After power on, input/output controller 602 monitors whether a user has entered a line input. Input/output controller 610 may be fast enough to detect in real time a stylus or finger, for example, has contacted a touch screen and follows the movements of the stylus in real time to determine whether a line is being input and whether objects are being crossed. When input/output controller 610 determines that a line has ended, the entered information may be sent to line shape discriminator 606 to determine whether particular line shapes have been drawn. Line shapes may also be determined in real time. If line shapes have been drawn, line shape discriminator 606 may convert various line shapes into codes, for example, and the line shape codes sent to command discriminator 608 to determine what command the user has entered.

[0043] Command discriminator 608 may transmit the commands to command processor 602 which in turn may access information from memory 604, process source data based on the commands, and output processed data into appropriate portions of memory 604. If the user commands require access of network resources, command processor 602 may access such resources via network interface 614. After the commands have been processed, command processor 602 may update display screen via display controller 612 to provide feedback to user of results of executed commands.

[0044] FIG. 19 shows a flowchart 700 of an exemplary process for processing lines as discussed above. For convenience of discussion, flowchart 700 assumes that the process is fast enough to follow in real time a stylus using a touch screen to enter commands, as an example.

[0045] After power on, the process starts by going to step 702 and determines whether a line input has begun. If a line input has begun, the process goes to step 704; otherwise, the process returns to step 702. In step 704, the process determines whether a line shape has been entered. If a line shape was entered, the process goes to step 708; otherwise, the process goes to step 706. In step 706, the process identifies a source for data based on the location of the start of the line. For example, if the line starts at an input area such as display section 208, the complete ink comment 222 may be determined to be the source. As discussed above, other types of icons may be used that may represent email, facsimile, instant messenger, etc., which may be selected by the start of the line.

[0046] In step 708, the process identifies the source based on the particular line shape entered and whether a command is also included. For example, if the line shape substantially surrounds a paragraph of a document, then the complete paragraph may be identified as the source data. If the line shape is a substantially straight line crossing out particular portions of an underlying text, then such text may be either copied or cut as determined by various parameters that may be initialized.

[0047] After step 706 or 708, the process goes to step 710. In step 710, the process determines whether a line shape is input that is not associated with a source/sink object. If such a line shape is entered, the process goes to step 712; otherwise, the process goes to step 716. In step 712, the process determines the type of line shape entered and identifies a command associated with the entered line shape. If no command is associated with the line shape, then the process may assume that a command was not intended and goes to step 716 without identifying a command, for example. In step 714, the process determines whether the line intersected an object. If the line intersected an object, the process goes to step 715; otherwise, the process goes to step 718. In step 715, the process determines whether the intersected object is a command or a source/sink object. If the object is a sink object, then the process goes to step 724; otherwise, the process goes to step 716. In step 716, the process identifies the command and queues the command for processing at an appropriate time and goes to step 718.

[0048] In step 718, the process determines whether the line has ended. If the line ended, the process goes to step 720; otherwise, the process returns to step 710. Thus, the process may accept multiple line shape/line-object sequences to perform complex functions. For example, the user may extend a line to surround particular text of an object to identify it as a source; then the line may further extend into another line shape that may be interpreted as a bold command so that the prior selected text is converted into bold font; then the line may further extend into another line shape that italicizes the selected text, and then the line may end at a sink object identifying a specific location so that the bolded and italicized selected text is placed at the identified location in the sink object. Thus, multiple commands may be selected to achieve combinations of operations that result in a complex process.

[0049] After step 118, the process goes to step 720. In step 720, the process determines whether a line shape has been entered at the end portion of the line. If a line shape was entered, the process goes to step 722; otherwise, the process goes to step 724. In step 722, the process identifies the command indicated by the line shape such as identifying a specific location to place the results of the commands. After step 722, the process goes to step 724. In step 724, the process may perform the commands identified by the line. While flowchart 700 indicates that commands are performed in step 724, depending on the type of command, the commands may be performed as they are identified or when all needed information is available. After step 724, the process goes to step 726. In step 726, the process determines whether the process has been turned off. If the process is turned off, the process goes to step 728 and ends; otherwise, the process returns to step 702 to detect whether a new line entry has begun.

[0050] The above-described user-machine interface may be applied in any context where a display screen is used. For example, in xerographic machines such as printers or copiers, a command panel is often available and may use the line system described above. When PDAs or cell phones are used, touch sensitive screen technology may be used so that a stylus or a user's finger, a pencil, etc., may be used to draw lines for interface with these small types of machines.

[0051] It will be appreciated that various of the above-disclosed and other features and functions, or alternatives thereof, may be desirably combined into many other different systems or applications. Also, various presently unforeseen or unanticipated alternatives, modifications, variations or improvements therein may be subsequently made by those skilled in the art, and are also intended to be encompassed by the following claims.