This application claims priority to and the benefit of application Ser. No. 13/649,948, entitled “SYSTEM AND METHOD FOR INTERACTING WITH A DISPLAYED WORK SPACE”, filed Oct. 11, 2012, which is herein incorporated by reference in its entirety for all purposes.
The present disclosure relates generally to an application interface that allows a user to adjust, modify, or otherwise interact with a work space available when using the application.
This section is intended to introduce the reader to various aspects of art that may be related to various aspects of the present disclosure, which are described and/or claimed below. This discussion is believed to be helpful in providing the reader with background information to facilitate a better understanding of the various aspects of the present disclosure. Accordingly, it should be understood that these statements are to be read in this light, and not as admissions of prior art.
Various applications implemented on electronic devices allow a user of the application to create some form of content and/or to perform problem solving. Such applications may provide delineated or discrete areas with which the user interacts or generates content. For example, in a database or spreadsheet application, these discrete work spaces may be provided in the form of columns or rows. Likewise, in other types of applications, such as for note taking or mathematical problem solving, discrete work spaces may be provided as rows, with each row providing space for an additional note or an additional step in a problem solving process.
In contexts where such an application is implemented on a computer or similar device, a keyboard and/or mouse may be available as input devices and the user may use these devices to interact with menus or other control elements of the interface to both interact with the discrete work spaces and/or to add or delete such work spaces. However, other types of electronic devices do not provide for the use of such separate input devices and/or have a limited amount of display area. In such instances, an interface that relies on menus and/or inputs from external devices may be infeasible or otherwise difficult to implement or use.
A summary of certain embodiments disclosed herein is set forth below. It should be understood that these aspects are presented merely to provide the reader with a brief summary of these certain embodiments and that these aspects are not intended to limit the scope of this disclosure. Indeed, this disclosure may encompass a variety of aspects that may not be set forth below.
The present disclosure provides for the use of application interfaces that allow a user to interact with a work space available to the user. For example, in certain implementations, an application interface is provided on an electronic device that includes a touch screen interface. In such an example, the application interface may include a defined display area that include one or more discrete works spaces with which a user interacts, such as rows and/or columns. In this example, the user can interact with the touch screen interface to drag or pull the defined display area beyond the defined scrollview or limitations associated with the application (i.e., an overscroll). In response to the overscroll event, the application may perform a specific action, such as adding one or more discrete work spaces (e.g., a row or a column) to the display area or performing a computational task. Thus, in one implementation, a user can add a row or a column to a defined work space with which he is interacting without utilizing a separate input device (e.g., a mouse or keyboard) and without interacting with a menu or other control interface structure. Likewise, the addition of the row or column is not based on any interaction with existing rows or columns.
Various aspects of this disclosure may be better understood upon reading the following detailed description and upon reference to the drawings in which:
One or more specific embodiments will be described below. In an effort to provide a concise description of these embodiments, not all features of an actual implementation are described in the specification. It should be appreciated that in the development of any such actual implementation, as in any engineering or design project, numerous implementation-specific decisions must be made to achieve the developers' specific goals, such as compliance with system-related and business-related constraints, which may vary from one implementation to another. Moreover, it should be appreciated that such a development effort might be complex and time consuming, but would nevertheless be a routine undertaking of design, fabrication, and manufacture for those of ordinary skill having the benefit of this disclosure.
The present disclosure relates to providing an application interface which may be used to add a row, column, or other discrete work spaces where data may be entered and/or manipulated. In certain implementations, a defined display area of the application interface is manipulated by a user to in an overscroll interaction whereby the defined display area is moved at least partially off beyond the scrollview limits associated with conventional interaction (e.g., data entry, manipulation, or review) with the display area. In response to the overscroll event, the application may add one or more rows and/or columns to the defined display area. The user may then enter data into or otherwise interact with the added row or column.
With the foregoing in mind, a general description is provided below of suitable electronic devices that may be used to implement an application having such functionality. In particular,
An example of an electronic device suitable for the techniques described herein may include various internal and/or external components. For example,
With regard to each of these components, the display 10 may be used to display various images generated by the device 8. The display 10 may be an LCD, OLED-type display, or other suitable display device. Additionally, in certain embodiments of the electronic device 8, the display 10 may be provided in conjunction with a touch-sensitive element, such as a touchscreen, that may be used as part of the control interface for the device 8.
The I/O ports 12 may include ports configured to connect to a variety of external devices, such as a power source, headset or headphones, or other electronic devices (such as handheld devices and/or computers, printers, projectors, external displays, modems, docking stations, and so forth). The I/O ports 12 may support any interface type, such as a universal serial bus (USB) port, a video port, a serial connection port, an IEEE-1394 or Firewire™ port, a Thunderbolt™ port, an Ethernet or modem port, and/or an AC/DC power connection port.
The input structures 14 may include the various devices, circuitry, and pathways by which user input or feedback is provided to the processor 16. Such input structures 14 may be configured to control a function of the device 8, applications running on the device 8, and/or any interfaces or devices connected to or used by the electronic device 8. For example, the input structures 14 may allow a user to navigate a displayed user interface or application interface. Examples of the input structures 14 may include buttons, sliders, switches, control pads, keys, knobs, scroll wheels, keyboards, mice, touchpads, internal accelerometers, and so forth.
In certain embodiments, an input structure 14 and display 10 may be provided together, such as in the case of a touchscreen where a touch sensitive mechanism is provided in conjunction with the display 10. In such embodiments, the user may select or interact with displayed interface elements via the touch sensitive mechanism. In this way, the displayed interface may provide interactive functionality, allowing a user to navigate the displayed interface by touching the display 10.
User interaction with the input structures 14, such as to interact with a user or application interface displayed on the display 10, may generate electrical signals indicative of the user input. These input signals may be routed via suitable pathways, such as an input hub or bus, to the processor(s) 16 for further processing.
The processor(s) 16 may provide the processing capability to execute the operating system, programs, user and application interfaces (e.g., an e-book user interface), and any other functions of the electronic device 8. The processor(s) 16 may include one or more microprocessors, such as one or more “general-purpose” microprocessors, one or more special-purpose microprocessors and/or ASICS, or some combination of such processing components. For example, the processor 16 may include one or more central processing units (CPUs), physics processors, graphics processors, video processors, audio processors and/or related chip sets.
The instructions or data to be processed by the processor(s) 16 may be stored in a computer-readable medium, such as a memory 18. Such a memory 18 may be provided as a volatile memory, such as random access memory (RAM), and/or as a non-volatile memory, such as read-only memory (ROM). The memory 18 may store a variety of information and may be used for various purposes. For example, the memory 18 may store firmware for the electronic device 8 (such as a basic input/output instruction or operating system instructions), various programs, applications, or routines executed on the electronic device 8, user interface functions, processor functions, and so forth. In addition, the memory 18 may be used for buffering or caching during operation of the electronic device 8.
The components may further include other forms of computer-readable media, such as a non-volatile storage 20, for persistent storage of data and/or instructions. The non-volatile storage 20 may include flash memory, a hard drive, or any other optical, magnetic, and/or solid-state storage media. The non-volatile storage 20 may be used to store firmware, data files, software, hardware configuration information, and any other suitable data.
The embodiment illustrated in
The components depicted in
Further, the components may also include a power source 26. In one embodiment, the power source 26 may be one or more batteries, such as a lithium-ion polymer battery or other type of suitable battery. The battery may be user-removable or may be secured within the housing of the electronic device 8 and may be rechargeable. Additionally, the power source 26 may include AC power, such as provided by an electrical outlet, and the electronic device 8 may be connected to the power source 26 via a power adapter. This power adapter may also be used to recharge one or more batteries, if present.
With the foregoing in mind,
In the depicted embodiment, the handheld device 30 is in the form of a tablet computer that may provide various functionalities (such as the ability to take pictures, record audio and/or video, listen to music, play games, map travel routes, and so forth). As discussed herein, one functionality provided by the handheld device 30 may be the execution of applications or routines, which may include the display of an application interface on display 10.
As discussed with respect to the general electronic device of
In the depicted embodiment, the handheld device 30 includes an enclosure or body that protects the interior components from physical damage and shields them from electromagnetic interference. The enclosure may be formed from any suitable material such as plastic, metal, or a composite material and may allow certain frequencies of electromagnetic radiation to pass through to wireless communication circuitry within the handheld device 30 to facilitate wireless communication.
In the depicted embodiment, the enclosure includes user input structures 14 through which a user may interface with the device. Each user input structure 14 may be configured to help control a device function when actuated. For example, in a table computer implementation, one or more of the input structures 14 may be configured to invoke a “home” screen or menu to be displayed, to toggle between a sleep and a wake mode, adjust the volume of audible feedback, and so forth.
In the depicted embodiment, the handheld device 30 includes a display 10 in the form of an LCD 32. The LCD 32 may be used to display a graphical user interface (GUI) 34 that allows a user to interact with the handheld device 30. The GUI 34 may include various layers, windows, screens, templates, or other graphical elements that may be displayed in all, or a portion, of the LCD 32. Generally, the GUI 34 may include graphical elements that represent applications and functions of the electronic device. The graphical elements may include icons 36 and other images representing buttons, sliders, menu bars, and the like. The icons 36 may correspond to various applications of the electronic device that may open upon selection of a respective icon 36. Furthermore, selection of an icon 36 may lead to a hierarchical navigation process, such that selection of an icon 36 leads to a screen that includes one or more additional icons or other GUI elements. The icons 36 may be selected via a touchscreen included in the display 10, or may be selected by a user input structure 14, such as a wheel or button.
The handheld electronic device 30 also may include various input and output (I/O) ports 12 that allow connection of the handheld device 30 to external devices. For example, one I/O port 12 may be a port that allows the transmission and reception of data or commands between the handheld electronic device 30 and another electronic device, such as a computer. Such an I/O port 12 may be a proprietary port from Apple Inc. or may be an open standard I/O port.
As discussed herein the electronic device 8, such as a handheld device 30, is capable of running an application having an application interface capable of being displayed on display 10. Turning to
While
In the example depicted in
With the application interface of
Turning to
In the depicted example, an input in the form of an overscroll event 82 is received or detected (step 84). As used herein, an overscroll or overscroll event 82 occurs when a user interacts with the defined display area 60 so as to cause the defined display area 60 to move or be moved beyond a limit (e.g., a defined scrollview) typically associated with the display of the defined display area 60. Upon detection of the overscroll event 82, the defined display area 60 is modified (step 86) based on one or more rules associated with the detection of the overscroll event 82. For example, in one embodiment the modified display area 88 may take the form of adding or subtracting discrete work spaces (e.g., rows and/or columns) to the defined display area 60 in accordance with one or more rules implemented by the application.
By way of example, and turning to
In certain implementations, an overscroll event may be associated with alternative actions or more than one threshold for action. For example, turning to
As will be appreciated, in other implementations other events may be associated with different extents of overscroll events 82. Likewise, overscroll events performed relative to different edges of the display area may be associated with different actions. For example, an overscroll event 82 associated with a right or left edges of the display (i.e., the right or left limits of the display or screen) may be associated with the addition or removal of columns to the defined display area 60. Likewise, an overscroll event 82 associated with the upper edge or limit of the display may be associated with the removal of one or more rows from the defined display area.
Turning back to the example provided in
However, in the example depicted in
The specific embodiments described above have been shown by way of example, and it should be understood that these embodiments may be susceptible to various modifications and alternative forms. It should be further understood that the claims are not intended to be limited to the particular forms disclosed, but rather to cover all modifications, equivalents, and alternatives falling within the spirit and scope of this disclosure.
Number | Name | Date | Kind |
---|---|---|---|
5592607 | Weber | Jan 1997 | A |
5592608 | Weber | Jan 1997 | A |
5740389 | Li et al. | Apr 1998 | A |
5786805 | Barry | Jul 1998 | A |
5812983 | Kumagai | Sep 1998 | A |
6065022 | Ueki | May 2000 | A |
8352286 | Bawa | Jan 2013 | B1 |
8607156 | Jania | Dec 2013 | B1 |
20020143831 | Bennett | Oct 2002 | A1 |
20050188352 | Jager | Aug 2005 | A1 |
20060224947 | Weber | Oct 2006 | A1 |
20080082938 | Buczek | Apr 2008 | A1 |
20080091752 | Powles | Apr 2008 | A1 |
20090007007 | Voros | Jan 2009 | A1 |
20090070711 | Kwak | Mar 2009 | A1 |
20090164602 | Kies | Jun 2009 | A1 |
20090288044 | Matthews et al. | Nov 2009 | A1 |
20100169760 | Hosokawa | Jul 2010 | A1 |
20100306130 | Fogelberg | Dec 2010 | A1 |
20110055752 | Rubinstein | Mar 2011 | A1 |
20120066621 | Matsubara | Mar 2012 | A1 |
20120081317 | Sirpal et al. | Apr 2012 | A1 |
20130006399 | Tandon | Jan 2013 | A1 |
20130014051 | Lefor | Jan 2013 | A1 |
20130135221 | Ainslie | May 2013 | A1 |
20130191220 | Dent | Jul 2013 | A1 |
20130283204 | Pasquero | Oct 2013 | A1 |
Number | Date | Country |
---|---|---|
0588686 | Sep 1993 | EP |
1703364 | Sep 2006 | EP |
2434388 | Mar 2012 | EP |
Number | Date | Country | |
---|---|---|---|
20150309688 A1 | Oct 2015 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13649948 | Oct 2012 | US |
Child | 14743741 | US |