Patent Application
20140215388
The present application relates generally to graphical user interfaces, and more particularly, some embodiments relate to resizable and lockable graphical user interfaces.
Electronic visual displays are ubiquitous and affecting people's lives significantly. Via user interfaces, a user interacts with electronic visual displays to select information of interest to be displayed. Nevertheless, information of more than one content may be displayed in one browser window or one tap of a browser window. For example, primary content such as articles are usually accompanied by secondary content such as promotional materials. Secondary content shares, with the primary content, the limited space of a browser window. Secondary content may distract the user from the primary content and diminish the user's experience with the primary content.
Resizable and lockable user interfaces are provided. Systems and methods described herein provide a user with the option to resize and/or fix a section of the user interface. A user may minimize interference and distraction caused by secondary content when traversing primary content. Because the secondary content shares the display area with the primary content, the display area for the primary content is increased as a result of the section being resized. The section may be locked or fixed to a defined area. As such, primary content and secondary content may be navigated separately. In various embodiments, a resizable and lockable user interface (UI) comprises a first section and a second section. The first section is configured to display a first content and the second section is configured to display a second content. The secondary section may be resized in response to a user's input.
The figures are provided for purposes of illustration only and merely depict typical or example embodiments. They do not limit the breadth, scope, or applicability of the invention.
Primary content and second content are usually displayed to a user in one browser window or one tap of a browser window. Visual designs, rather than user interfaces (UIs), are usually relied on to differentiate primary content from secondary content. Nevertheless, when a user interacts with the primary content, it is inevitable that the secondary content may also be navigated. The primary content cannot be separated from the secondary content and the user's experience with the primary content is usually compromised.
The first section 102 and the second 103 share the display area of the visual display device 100. The resizable and lockable UI 101 comprises a set of UI controls 110-123. UI controls may include screen buttons of various shapes and appearances. Example UI controls 111-123 are buttons 111-123 that may be tapped or clicked by the user to access information of the primary or the secondary content. The UI control 110 is configured to track a motion of a user's finger(s), a stylus, or other similar objects. The motion may take place at different locations on the display screen of the visual display device 100. In the illustrated example, the motion is located in the middle of the screen of the visual display device 100. The UI control 110 may enable resizing and/or locking of the secondary section 103. A UI may include traditional navigation elements such as, for example scroll left/right, scroll up/down, back, zoom in/out, double click, multi-touch, and so on.
The UI control 110 allows a user to navigate, resize the second section 103, and/or lock the second section 103. In the illustrated example, the UI control 110 allows a user to slide up thereby bringing up both the primary content displayed in the first section 102 and the secondary content displayed in the second section 103. The user may resize the second section 103. For example, by performing a resizing gesture (e.g., a quick slide, a tap, or other triggering actions), the second section 103 may be resized. In some embodiments, a user may swipe in a direction (e.g., a horizontal direction, a vertical direction) to define the location for the boundary 104 between the first section 102 and the second section 103. In other embodiments, a user may actuate the UI control 110 by sliding up until the boundary 104 between the first section 102 and the second section 103 reaches the top edge 105 of the display area of the visual display device 100.
In the illustrated example, the second section 103 may be resized to an area defined by the top edge 105 of the display area of the visual display device 100 and the boundary 104 between the first section 102 and the second section 103. In various embodiments, the resized second section may be locked or fixed such that it is unresponsive to any input that is not a disabling or unlocking motion or gesture. In one embodiment, sliding anywhere on the display that lacks content (e.g., a background area) may unlock a second section that is fixed or locked. The first section as well as the displayed primary content may be adjusted in response to resizing of the second section 103.
In various embodiments, the secondary content to be displayed in the second section 103 is adjusted according to the size of the second section 103. In various embodiments, second content may be prioritized. Where the display area is limited, the content with a higher priority rather than the content with a lower priority may be displayed. In other words, the lower priority content is not displayed unless the display area is sufficient for displaying such content. In one example, the movie title of a movie being promoted has the highest priority and may be displayed instead of other promotional materials when the second section 103 is resized.
In various embodiments, a user's input may define the first section 102 and the second section 103 of a UI 101. For example, a user may draw a line such as the boundary 104 to divide the UI 101 into two sections. Subsequently, the user may define the first section 102 to display primary content and the second section 103 to display secondary content. In one embodiment, a user input defines the first and second sections only if a display area is defined. In the illustrated example, the display area is the entire screen space of the visual display 100. In some embodiments, a user may define an area of the screen space to be a display area. The predefined display area may be provided by non-user entities, for example, the developers of the application.
The resizing and/or locking of the second section 103 may be temporary. That is, a user may disable resizing and/or locking of the second section 103 and restore the second section 103 to its original size. The UI 101 is displayed according to its original design. By performing an unlocking gesture (e.g., a quick slide, a tap, or other triggering actions), a user may choose to restore the second section 103 to its original size. Upon receiving the disabling and/or unlocking input from the user, the second section 103 is no longer resized. After disabling resizing of the second section 103, the user may then navigate the content of both the primary and secondary sections 102-103. The first section 102 may be readjusted after disabling the resizing of the second section 103 in order to recover the UI 101 to its original design.
In the illustrated example, only the first section 102 is displayed on the screen space of the electronic visual display 100. In various embodiments, the first section 102 and the primary content displayed in the first section 102 may be adjusted. Compared with
In order to trigger a resizing of the second section 103, a user may slide up both sections until the boundary 104 between the first section 102 and the second section 103 reaches the top edge 105 of the display area of the visual display device 100. A user may swipe up swiftly to fix the boundary 104 to the top edge 105 thereby locking the size of the second section 103 to the temporary size, which is zero in the illustrated example. In one embodiment, a user may draw a line across the display area to define the new position for the boundary 104 and swipe up swiftly, tap the screen swiftly, or employ a multi-finger motion thereby locking the size of the second section 103 to the temporary size.
While a second section 103 is being resized, content displayed in the second section 103 may be adjusted simultaneously according to the instant size of the second section 103. In various embodiments, content may be prioritized such that depending on the area of the second section 103, content with the priority above a threshold priority is displayed. As such, content of the highest priority disappears last in the second section 103 while the second section 103 is being resized. When a second section 103 is resized, primary content displayed in the first section 102 and secondary content displayed in the second section 103 may be both navigated via UI controls and/or traditional navigation elements. When a second section 103 is resized and fixed, only content of the first section 102 may be navigated via UI controls and/or traditional navigation elements.
In the illustrated example, as the second section 103 is resized to be completely “hidden” (i.e., the second section 103 is resized to zero and fixed), no secondary content is displayed in the second section 103. When a user navigates the user interface 101 in
In the illustrated examples, the second section 103 is above the first section 102. In other embodiments, a first section and a second section may be configured in other positions relative to each other. For example, the second section 103 may be below, to the right, or to the left of the first section 102. In various embodiments, each of the first section and the second section may comprise a plurality of sub-sections corresponding to different display areas. The secondary display area and the primary display area may be positioned in various arrangements.
Turning now to
The application software 146 may include software that provides additional functionality to the device. In some embodiments, the application software 146 may include applications to provide browsing and navigation features such as those described herein. As described herein, the application software 146 may be downloaded to the device such as via a communication interface 140 (described below) or it may be preinstalled in memory 138 of the display device 122.
As shown, the example display device 122 includes a display 132. The display 132 may form part of the display device 122, or it may be a separate hardware component that is connected to the display device 122. For example, the display 132 may be a touch screen display, which is part of the iPad® device and/or a smart TV.
The example display device 122 also includes a processor 142 and memory 138. The memory 138 may include volatile memory such as some form of random access memory, and it may include non-volatile memory such as flash memory or a hard disk drive. The processor 142 may be a conventional central processing unit (CPU) such as those manufactured by AMD®, and Intel®, or it may be a specialized processor. The processor 142 may be configured to execute computer instructions from the operating system software 144, application software 146, or other software stored in the memory 138.
The display device 122 may also include a communication interface 140. The communication interface 140 may take the form of a network interface chip or card and its corresponding driver software that allows the display device 122 to communicate with external networks. For example, the communication interface 140 can include communication interfaces to support communication protocols such as Bluetooth®, WiFi® or other wireless or wired protocols. The display device 122 may further include a card reader or other memory device reader 136 capable of reading removable memory cards such as, for example, SD cards, thumb drives and the like.
As used herein, the term module might describe a given unit of functionality that can be performed in accordance with one or more embodiments of the present application. As used herein, a module might be implemented utilizing any form of hardware, software, or a combination thereof. For example, one or more processors, controllers, ASICs, PLAs, PALs, CPLDs, FPGAs, logical components, software routines or other mechanisms might be implemented to make up a module. In implementation, the various modules described herein might be implemented as discrete modules or the functions and features described can be shared in part or in total among one or more modules. In other words, as would be apparent to one of ordinary skill in the art after reading this description, the various features and functionality described herein may be implemented in any given application and can be implemented in one or more separate or shared modules in various combinations and permutations. Even though various features or elements of functionality may be individually described or claimed as separate modules, one of ordinary skill in the art will understand that these features and functionality can be shared among one or more common software and hardware elements, and such description shall not require or imply that separate hardware or software components are used to implement such features or functionality.
Where components or modules of the application are implemented in whole or in part using software, in one embodiment, these software elements can be implemented to operate with a computing or processing module capable of carrying out the functionality described with respect thereto. One such example computing module is shown in
Referring now to
Computing module 300 might include, for example, one or more processors, controllers, control modules, or other processing devices, such as a processor 304. Processor 304 might be implemented using a general-purpose or special-purpose processing engine such as, for example, a microprocessor, controller, or other control logic. In the illustrated example, processor 304 is connected to a bus 302, although any communication medium can be used to facilitate interaction with other components of computing module 300 or to communicate externally.
Computing module 300 might also include one or more memory modules, simply referred to herein as main memory 308. For example, preferably random access memory (RAM) or other dynamic memory, might be used for storing information and instructions to be executed by processor 304. Main memory 308 might also be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 304. Computing module 300 might likewise include a read only memory (“ROM”) or other static storage device coupled to bus 302 for storing static information and instructions for processor 304.
The computing module 300 might also include one or more various forms of information storage mechanism 310, which might include, for example, a media drive 312 and a storage unit interface 320. The media drive 312 might include a drive or other mechanism to support fixed or removable storage media 314. For example, a hard disk drive, a floppy disk drive, a magnetic tape drive, an optical disk drive, a CD or DVD drive (R or RW), or other removable or fixed media drive might be provided. Accordingly, storage media 314 might include, for example, a hard disk, a floppy disk, magnetic tape, cartridge, optical disk, a CD or DVD, or other fixed or removable medium that is read by, written to or accessed by media drive 312. As these examples illustrate, the storage media 314 can include a computer usable storage medium having stored therein computer software or data.
In alternative embodiments, information storage mechanism 310 might include other similar instrumentalities for allowing computer programs or other instructions or data to be loaded into computing module 300. Such instrumentalities might include, for example, a fixed or removable storage unit 322 and an interface 320. Examples of such storage units 322 and interfaces 320 can include a program cartridge and cartridge interface, a removable memory (for example, a flash memory or other removable memory module) and memory slot, a PCMCIA slot and card, and other fixed or removable storage units 322 and interfaces 320 that allow software and data to be transferred from the storage unit 322 to computing module 300.
Computing module 300 might also include a communications interface 324. Communications interface 324 might be used to allow software and data to be transferred between computing module 300 and external devices. Examples of communications interface 324 might include a modem or softmodem, a network interface (such as an Ethernet, network interface card, WiMedia, IEEE 802.XX or other interface), a communications port (such as for example, a USB port, IR port, RS232 port Bluetooth® interface, or other port), or other communications interface. Software and data transferred via communications interface 324 might typically be carried on signals, which can be electronic, electromagnetic (which includes optical) or other signals capable of being exchanged by a given communications interface 324. These signals might be provided to communications interface 324 via a channel 328. This channel 328 might carry signals and might be implemented using a wired or wireless communication medium. Some examples of a channel might include a phone line, a cellular link, an RF link, an optical link, a network interface, a local or wide area network, and other wired or wireless communications channels.
In this document, the terms “computer program medium” and “computer usable medium” are used to generally refer to transitory or non-transitory media such as, for example, memory 308, storage unit 320, media 314, and channel 328. These and other various forms of computer program media or computer usable media may be involved in carrying one or more sequences of one or more instructions to a processing device for execution. Such instructions embodied on the medium, are generally referred to as “computer program code” or a “computer program product” (which may be grouped in the form of computer programs or other groupings). When executed, such instructions might enable the computing module 300 to perform features or functions of the present application as discussed herein.
Although described above in terms of various exemplary embodiments and implementations, it should be understood that the various features, aspects and functionality described in one or more of the individual embodiments are not limited in their applicability to the particular embodiment with which they are described, but instead can be applied, alone or in various combinations, to one or more of the other embodiments of the application, whether or not such embodiments are described and whether or not such features are presented as being a part of a described embodiment. Thus, the breadth and scope of the present application should not be limited by any of the above-described exemplary embodiments.
Terms and phrases used in this document, and variations thereof, unless otherwise expressly stated, should be construed as open ended as opposed to limiting. As examples of the foregoing: the term “including” should be read as meaning “including, without limitation” or the like; the term “example” is used to provide exemplary instances of the item in discussion, not an exhaustive or limiting list thereof; the terms “a” or “an” should be read as meaning “at least one,” “one or more” or the like; and adjectives such as “conventional,” “traditional,” “normal,” “standard,” “known” and terms of similar meaning should not be construed as limiting the item described to a given time period or to an item available as of a given time, but instead should be read to encompass conventional, traditional, normal, or standard technologies that may be available or known now or at any time in the future. Likewise, where this document refers to technologies that would be apparent or known to one of ordinary skill in the art, such technologies encompass those apparent or known to the skilled artisan now or at any time in the future.
The presence of broadening words and phrases such as “one or more,” “at least,” “but not limited to” or other like phrases in some instances shall not be read to mean that the narrower case is intended or required in instances where such broadening phrases may be absent. The use of the term “module” does not imply that the components or functionality described or claimed as part of the module are all configured in a common package. Indeed, any or all of the various components of a module, whether control logic or other components, can be combined in a single package or separately maintained and can further be distributed in multiple groupings or packages or across multiple locations.
Additionally, the various embodiments set forth herein are described in terms of exemplary block diagrams, flow charts and other illustrations. As will become apparent to one of ordinary skill in the art after reading this document, the illustrated embodiments and their various alternatives can be implemented without confinement to the illustrated examples. For example, block diagrams and their accompanying description should not be construed as mandating a particular architecture or configuration.
This application claims the benefit of U.S. Provisional Application No. 61/759,383, filed on Jan. 31, 2013, which is hereby incorporated herein by reference in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| 61759383 | Jan 2013 | US |
