Modern computing systems are provided with a wide variety of input and output (I/O) mechanisms for allowing a user to interact with stored data. Depending on the operational setting, a given I/O mechanism will result in various benefits and/or limitations for the user-device interaction. Devices that are portable and/or that employ touch sensitive interfaces can pose particular challenges to the design and deployment of I/O mechanisms.
Normally, it is desirable that portable devices be relatively small, which can limit the ability to provide powerful input mechanisms that are easy to use. For example, in the design of laptop/notebook computers and mobile phones, screen size is often sacrificed in order to improve portability. The smaller screen size can limit touch screen input capability, and in general decreases the utility of the device when performing tasks that are well-suited to large screen sizes. Functionalities that often suffer due to these tradeoffs are document creation, and sharing and collaboration among multiple users/participants.
A touch sensitive computing system is provided. The computing system is provided with various interface features providing numerous advantages in a variety of settings. In particular, the system includes a first touch sensitive display and a second touch sensitive display, both of which are operatively coupled with a processing subsystem, and with a memory subsystem which stores a plurality of content pages. User interface instructions are stored in the memory subsystem and are executable by the processing subsystem to provide user interactivity with the content pages through the first touch sensitive display and the second touch sensitive display. The interface instructions are further configured to control the displays so that they operate as discretely organized interface units for the content pages. Typically, the interface instructions cause one of the displays to operate as a touch sensitive freeform interface for editing one of the content pages, while the other is controlled to provide a navigable overview of the content pages, or a more structured interface for performing editing and viewing functions.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to implementations that solve any or all disadvantages noted in any part of this disclosure.
Referring to
In many of the examples discussed herein, user interactivity is provided via display subsystem 32, which typically is touch sensitive and includes multiple displays. For example, in
Generally, as will be further illuminated in the examples below, one of the displays 34 and 36 provides navigation and more structured user interface controls, while the other provides a touch sensitive freeform interface for modifying individual content pages. Typically, the separate and discretely organized interfaces provided by the displays are implemented so that one of the displays is a relatively more structured and constrained interface, with the other being relatively less so.
Input mechanisms are one category of interface features that may be used to describe the degree to which an interface unit is structured, as opposed to unstructured. For example, in a relatively more structured interface, buttons and/or menu selections (e.g., from pull-down menus) may be used to perform selection and editing operations on a displayed page, such as cut, copy, paste, rotate, crop, etc. For text entry, the structured interface might include a QWERTY keyboard or similar button/key-based method of text entry. For drawing operations, the user may select from clip art, template shapes or other displayed collections of predefined objects.
On the other hand, an unstructured interface would rely exclusively, or at least to a much greater degree, upon freeform inputs, such as handtouch inputs, interpreted gesture commands, and freeform touch inputs effected via user manipulation of a stylus or other pen-type implement.
Referring still to
Turning now to
Referring particularly to content page 60, the example page includes a graphical image 70, a block of text 72 (for example, describing the graphical image 70) and a flowchart 74.
Turning first to structured interface 62, the interface includes various structured input mechanisms for creating and modifying content pages. In particular, the interface may include a template 80 containing various shapes, graphics etc. that can be selected for inclusion on content page 60, for example via a drag and drop operation or by selection and copying. For example, flowchart 74 may be constructed using standard shapes and components found in template 80.
Structured interface 62 may also include a keyboard 82 to enable entry of alpha-numeric text data, such as text block 72. The structured interface may also include other structured input mechanisms, such as pull-down menus or toolbars 84 and 86, to perform copy, cut, paste, move, rotate, crop, etc. operations. The structured interface may also include a scrolling actuator 88 to perform vertical scrolling or other constrained scrolling operations.
Various other input mechanisms and controls may be provided in connection with the structured interface. The above examples are illustrative only. In general, the interface is structured in the sense that the commands and operations that are available are discrete and/or presented to the user in a structured format, and the specific inputs processed to initiate the commands are quantized or otherwise discrete.
Referring now to the unstructured, or freeform interface 64 of
The freeform nature of interface 64 also means that some processing may occur to interpret user inputs and produce the desired command. Referring to the exemplary flowchart 74, freeform inputs may be used to generate the depicted shapes. For example, the interface could be configured so that an oval is created by using pen-type implement 92 to freehand draw an oval. Being freehand, the drawing input would likely be imperfect. The interface would nonetheless process the input and recognize the user's intention to create an oval. In contrast to the structured method of selecting an oval from template 80 (structured interface 62), a large and continuously variable range of sketched drawing inputs could be used in interface 64 to create an oval.
Accordingly, it will be appreciated that user interface instructions 40 (
In addition to providing structured and unstructured interfaces for working with individual content pages, the displays of touch sensitive computing system 20 may be configured to provide an overview interface for content pages 42.
As previously discussed, touch sensitive computing system may be configured so that displays 34 and 36 operate as discretely organized interface units with respect to content pages 42. The provision of multiple displays (two in the present examples) that operate separately and discretely in terms of their interface can provide numerous advantages. For example, referring to
The ready availability of both structured and unstructured access to the page allows the device to leverage the benefits of digital technology, while also allowing the user to relate to the device and interact with it in a more natural and flexible way. The inventors have noted the persistent use of pen and paper for sketching, note-taking and other freeform tasks, despite the continued improvement and ever-increasing use of portable electronic devices. It is contemplated that the described interface systems and methods will provide a significantly enhanced user experience in certain settings, such that the example devices discussed herein will perform well for tasks where paper-and-pen solutions are still preferred.
The provision of multiple, discretely organized interface units can also provide benefits in settings where multiple users are collaborating. One example benefit is the ability to allow multiple users to modify or annotate a content page through separate interfaces, and use the different interfaces to identify the user responsible for the particular change or contribution. For example, the editing interface on display 34 might be assigned to User A, while the interface on display 36 would be assigned to User B.
Another example of multiple, discretely organized interface units is shown in
Referring now to
Continuing with exemplary method 130, where a freeform interface is employed it will often be desirable to use pentouch inputs, as shown at 136. At 138, the method may further include processing the pentouch inputs so that they result in performing one of a plurality of predefined modifications to a displayed content page.
It will be appreciated that the computing devices described herein may be any suitable computing device configured to execute the programs described herein. For example, the computing devices may be a mainframe computer, personal computer, laptop computer, portable data assistant (PDA), computer-enabled wireless telephone, networked computing device, or other suitable computing device, and may be connected to each other via computer networks, such as the Internet. These computing devices typically include a processor and associated volatile and non-volatile memory, and are configured to execute programs stored in non-volatile memory using portions of volatile memory and the processor. As used herein, the term “program” refers to software or firmware components that may be executed by, or utilized by, one or more computing devices described herein, and is meant to encompass individual or groups of executable files, data files, libraries, drivers, scripts, database records, etc. It will be appreciated that computer-readable media may be provided having program instructions stored thereon, which upon execution by a computing device, cause the computing device to execute the methods described above and cause operation of the systems described above.
It should be understood that the embodiments herein are illustrative and not restrictive, since the scope of the invention is defined by the appended claims rather than by the description preceding them, and all changes that fall within metes and bounds of the claims, or equivalence of such metes and bounds thereof are therefore intended to be embraced by the claims.
Number | Name | Date | Kind |
---|---|---|---|
5274758 | Beitel et al. | Dec 1993 | A |
5276796 | Yamada et al. | Jan 1994 | A |
6639606 | Choi | Oct 2003 | B1 |
7262763 | Kinjo | Aug 2007 | B2 |
20050024341 | Gillespie et al. | Feb 2005 | A1 |
20050052835 | Wu et al. | Mar 2005 | A1 |
20060026536 | Hotelling et al. | Feb 2006 | A1 |
20060034042 | Hisano et al. | Feb 2006 | A1 |
20060064643 | Hariton | Mar 2006 | A1 |
20070085759 | Lee et al. | Apr 2007 | A1 |
20070168855 | Patel et al. | Jul 2007 | A1 |
20070188473 | Anwar | Aug 2007 | A1 |
20080115080 | Matulic | May 2008 | A1 |
20080301542 | McGee et al. | Dec 2008 | A1 |
20090244016 | Casparian et al. | Oct 2009 | A1 |
Entry |
---|
Shea, Dan, “Planet PDF”, “Tiling PDF Documents across Two Screens in Acrobat”, retrieved at <<http://www.planetpdf.com/enterprise/article.asp?ContentID=Tiling—PDF—documents—across—two—screens—in—Acrobat>>, May 25, 2006, pp. 3. |
Chen, et al., “Navigation Techniques for Dual-Display E-Book Readers”, retrieved at <<http://www.cs.umd.edu/˜nchen/papers/p1779.pdf>>, CHI 2008, Apr. 5-10, 2008, pp. 1779-1788. |
“International Search Report”, Mailed Date: Oct. 26, 2010, Application No. PCT/US2010/027229, Filed Date: Mar. 12, 2010, pp. 9. |
Number | Date | Country | |
---|---|---|---|
20100245256 A1 | Sep 2010 | US |