Electronic device and method of displaying information in response to input

Information

  • Patent Grant
  • 9766718
  • Patent Number
    9,766,718
  • Date Filed
    Monday, February 28, 2011
    13 years ago
  • Date Issued
    Tuesday, September 19, 2017
    7 years ago
Abstract
A method includes displaying, in a window or field, first information associated with a first source running on a portable electronic device and detecting an input to display second information associated with a second source. After the detecting, second information associated with the second source and the first information in the window or field is displayed.
Description
FIELD OF TECHNOLOGY

The present disclosure relates to electronic devices, including but not limited to, portable electronic devices having touch-sensitive displays and their control.


BACKGROUND

Electronic devices, including portable electronic devices, have gained widespread use and may provide a variety of functions including, for example, telephonic, electronic messaging and other personal information manager (PIM) application functions. Portable electronic devices include, for example, several types of mobile stations such as simple cellular telephones, smart telephones, wireless personal digital assistants (PDAs), and laptop computers with wireless 802.11 or Bluetooth capabilities.


Portable electronic devices such as PDAs or smart telephones are generally intended for handheld use and ease of portability. Smaller devices are generally desirable for portability. A touch-sensitive display, also known as a touchscreen display, is particularly useful on handheld devices, which are small and have limited space for user input and output. The information displayed on the touch-sensitive displays may be modified depending on the functions and operations being performed. With continued demand for decreased size of portable electronic devices, touch-sensitive displays continue to decrease in size.


Improvements in devices with touch-sensitive displays are desirable.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a block diagram of a portable electronic device in accordance with the disclosure.



FIG. 2 is a sectional side view of a portable electronic device with a mechanical actuator in accordance with the disclosure.



FIG. 3 is a sectional side view of a portable electronic device with a depressed mechanical actuator in accordance with the disclosure.



FIG. 4 is a sectional side view of a portable electronic device with piezoelectric actuators in accordance with the disclosure.



FIG. 5 is a sectional side view of a portable electronic device with depressed piezoelectric actuators in accordance with the disclosure.



FIG. 6 is a flowchart illustrating a method of displaying information for a plurality of applications in accordance with the disclosure.



FIG. 7, FIG. 8, FIG. 9, FIG. 10, and FIG. 11 illustrate examples of displaying information for a plurality of applications in accordance with the disclosure.





DETAILED DESCRIPTION

The following describes an apparatus for and method of displaying information for a plurality of applications. While information for one application is displayed, a gesture is detected, and information for another application is displayed at an end of the original application. For example, while in an email application, when the gesture is detected, information associated with a calendar is displayed after the email application information is displayed. Thus, a user is provided with a quick way to open an additional application or preview information from the additional application without having to navigate to select an icon or enter a menu. The information may be displayed on any electronic device, including, for example, a portable electronic device.


For simplicity and clarity of illustration, reference numerals may be repeated among the figures to indicate corresponding or analogous elements. Numerous details are set forth to provide an understanding of the embodiments described herein. The embodiments may be practiced without these details. In other instances, well-known methods, procedures, and components have not been described in detail to avoid obscuring the embodiments described. The description is not to be considered as limited to the scope of the embodiments described herein.


The disclosure generally relates to an electronic device, which is a portable electronic device in the embodiments described herein. Examples of portable electronic devices include mobile, or handheld, wireless communication devices such as pagers, cellular phones, cellular smart-phones, wireless organizers, personal digital assistants, wirelessly enabled notebook computers, tablet computers, and so forth. The portable electronic device may also be a portable electronic device without wireless communication capabilities, such as a handheld electronic game device, digital photograph album, digital camera, or other device.


A block diagram of an example of a portable electronic device 100 is shown in FIG. 1. The portable electronic device 100 includes multiple components, such as a processor 102 that controls the overall operation of the portable electronic device 100. Communication functions, including data and voice communications, are performed through a communication subsystem 104. Data received by the portable electronic device 100 is decompressed and decrypted by a decoder 106. The communication subsystem 104 receives messages from and sends messages to a wireless network 150. The wireless network 150 may be any type of wireless network, including, but not limited to, data wireless networks, voice wireless networks, and networks that support both voice and data communications. A power source 142, such as one or more rechargeable batteries or a port to an external power supply, powers the portable electronic device 100.


The processor 102 interacts with other components, such as Random Access Memory (RAM) 108, memory 110, a display 112 with a touch-sensitive overlay 114 operably coupled to an electronic controller 116 that together comprise a touch-sensitive display 118, one or more actuators 120, one or more force sensors 122, an auxiliary input/output (I/O) subsystem 124, a data port 126, a speaker 128, a microphone 130, short-range communications 132, and other device subsystems 134. User-interaction with a graphical user interface is performed through the touch-sensitive overlay 114. The processor 102 interacts with the touch-sensitive overlay 114 via the electronic controller 116. Information, such as text, characters, symbols, images, icons, and other items that may be displayed or rendered on a portable electronic device, is displayed on the touch-sensitive display 118 via the processor 102. The processor 102 may interact with an accelerometer 136 that may be utilized to detect direction of gravitational forces or gravity-induced reaction forces.


To identify a subscriber for network access, the portable electronic device 100 uses a Subscriber Identity Module or a Removable User Identity Module (SIM/RUIM) card 138 for communication with a network, such as the wireless network 150. Alternatively, user identification information may be programmed into memory 110.


The portable electronic device 100 includes an operating system 146 and software programs or components 148 that are executed by the processor 102 and are typically stored in a persistent, updatable store such as the memory 110. Additional applications or programs may be loaded onto the portable electronic device 100 through the wireless network 150, the auxiliary I/O subsystem 124, the data port 126, the short-range communications subsystem 132, or any other suitable subsystem 134.


A received signal such as a text message, an e-mail message, or web page download is processed by the communication subsystem 104 and input to the processor 102. The processor 102 processes the received signal for output to the display 112 and/or to the auxiliary I/O subsystem 124. A subscriber may generate data items, for example e-mail messages, which may be transmitted over the wireless network 150 through the communication subsystem 104. For voice communications, the overall operation of the portable electronic device 100 is similar. The speaker 128 outputs audible information converted from electrical signals, and the microphone 130 converts audible information into electrical signals for processing.


The touch-sensitive display 118 may be any suitable touch-sensitive display, such as a capacitive, resistive, infrared, surface acoustic wave (SAW) touch-sensitive display, strain gauge, optical imaging, dispersive signal technology, acoustic pulse recognition, and so forth, as known in the art. A capacitive touch-sensitive display includes a capacitive touch-sensitive overlay 114. The overlay 114 may be an assembly of multiple layers in a stack including, for example, a substrate, a ground shield layer, a barrier layer, one or more capacitive touch sensor layers separated by a substrate or other barrier, and a cover. The capacitive touch sensor layers may be any suitable material, such as patterned indium tin oxide (ITO).


One or more touches, also known as touch contacts or touch events, may be detected by the touch-sensitive display 118. The processor 102 may determine attributes of the touch, including a location of a touch. Touch location data may include an area of contact or a single point of contact, such as a point at or near a center of the area of contact. A signal is provided to the controller 116 in response to detection of a touch. A touch may be detected from any suitable contact member, such as a finger, thumb, appendage, or other objects, for example, a stylus, pen, or other pointer, depending on the nature of the touch-sensitive display 118. Multiple simultaneous touches may be detected.


One or more actuators 120 may be depressed or activated by applying sufficient force to the touch-sensitive display 118 to overcome the actuation force of the actuator 120. The actuator(s) 120 may be actuated by pressing anywhere on the touch-sensitive display 118. The actuator(s) 120 may provide input to the processor 102 when actuated. Actuation of the actuator(s) 120 may result in provision of tactile feedback. When force is applied, the touch-sensitive display 118 is depressible, pivotable, and/or movable. Such a force may actuate the actuator(s) 120. The touch-sensitive display 118 may, for example, float with respect to the housing of the portable electronic device, i.e., the touch-sensitive display 118 may not be fastened to the housing. The actuator may be any suitable actuator, including mechanical and/or electrical actuators.


A sectional side view of a portable electronic device 100 with a mechanical actuator 120 is shown in FIG. 2. The cross section is taken through the center of the actuator 120. The portable electronic device 100 includes a housing 202 that encloses components such as shown in FIG. 1. A base 210 extends between the sidewalls of the housing and supports the actuator 120, which is a mechanical dome switch actuator in the example of FIG. 2. For a mechanical dome switch/actuator, tactile feedback is provided when the dome collapses due to imparted force and when the dome switch/actuator returns to the rest position after release of the switch.


Alternatively, the actuator 120 may comprise one or more piezoelectric (piezo) devices 402 that provide tactile feedback for the touch-sensitive display 118. Contraction of the piezo actuator 120 applies a spring-like force, for example, opposing a force externally applied to the touch-sensitive display 118. Each piezo actuator includes a piezoelectric device 402, such as a piezoelectric ceramic disk adhered to a substrate 404 that may comprise metal and/or another flexible or elastically deformable material. The substrate 404 bends when the piezo device 402 contracts due to charge/voltage across the piezo device 402 or in response to a force, such as an external force applied to the touch-sensitive display 118. The charge/voltage may be adjusted by varying the applied voltage or current, thereby controlling the force applied by the piezo device 402. The charge/voltage may advantageously be removed over a relatively short period of time to provide tactile feedback. An element 408 and an optional force sensor 122 may be disposed between the piezo actuator 402 and the touch-sensitive display 118 to facilitate actuation of the piezo actuator and/or the optional force sensors 122. The piezo actuators 120 may be controlled to provide various forms of tactile feedback, for example, a vibration to notify of an incoming call or text message or simulation of a dome switch upon depression of the touch-sensitive display 118.


The touch-sensitive display 118 is moveable and depressible with respect to the housing 202, and is shown floating with respect to, i.e., not fastened to, the housing 202 in the examples of FIG. 2 through FIG. 5. As the touch-sensitive display 118 moves toward the base 210, the actuator 120 is depressed or actuated as shown in FIG. 3 and FIG. 5, for example, in response to a force 302, 502 applied to the touch-sensitive display 118. The processor 102 receives a signal when the actuator 120 is depressed or actuated, which signal may trigger a selection or other input to the portable electronic device 100.


Force information related to a detected touch may be utilized to select information, such as information associated with a location of a touch. For example, a touch that does not meet a force threshold may highlight a selection option, whereas a touch that meets a force threshold may select or input that selection option. Selection options include, for example, displayed or virtual keys of a keyboard; selection boxes or windows, e.g., “cancel,” “delete,” or “unlock”; function buttons, such as play or stop on a music player; and so forth. Different magnitudes of force may be associated with different functions or input. For example, a lesser force may result in panning, and a higher force may result in zooming. Force as utilized throughout the specification, including the claims, refers to force measurements, estimates, and/or calculations, such as pressure, deformation, stress, strain, force density, force-area relationships, thrust, torque, and other effects that include force or related quantities.


Typically, when a user views information while in an application on a portable electronic device 100, information for that application alone is displayed in the window, also known as a field, where the application is open or launched. As described below, that same window may be utilized to at least temporarily display information from one or more additional sources or applications. Given the relatively small area available for display on a portable electronic device 100, the window is typically the display area, except for area that may be utilized as a header, a footer, and so forth. Unlike larger computer monitors, viewing information on existing portable devices for two applications is typically performed by displaying one application at a time due to the smaller display size. As described below, the same window or display area may be utilized to continuously view information from multiple sources, such as applications. For example, while received emails are displayed, a user may need to view future actions, such as calendar events or tasks. When an appropriate input, such as a gesture is received, upcoming calendar events may be viewed continuously with the emails as described below. For example, emails displayed with the most recently received email on top may be viewed effectively continuously with the nearest calendar event displayed on the bottom or nearest to the most recently received email. Information from multiple sources or applications may be displayed in a single window or field, where information may be combined in a useful manner, such as by time, by contact, by other parameter or category, and so forth. For example, a single stream of information can be viewed in chronological order, with the future actions being optionally selected for viewing.


A flowchart illustrating a method of displaying information for a plurality of applications of an electronic device is shown in FIG. 6. The method may be carried out by software executed, for example, by the processor 102. Coding of software for carrying out such a method is within the scope of a person of ordinary skill in the art given the present description. The method may contain additional or fewer processes than shown and/or described, and may be performed in a different order. Computer-readable code executable by at least one processor of the portable electronic device to perform the method may be stored in a computer-readable medium.


Information associated with a first source, such as a first application, referred to as first information, is displayed 602 on a display, for example, on a touch-sensitive display 118. The information may be information associated with any suitable source or application, such as email, text messaging, calendar, tasks, address book or contacts, media player, or any other suitable application in which information is displayed by an electronic device 100. Information associated with email may include a list of email messages, information associated with a calendar may include meeting schedule, calendar day view, week view, month view, or agenda view, information associated with an address book may include a listing of contacts, information associated with a media player may include text, pictures, videos, or artwork related to music or other media. The information is not limited to the examples provided.


An input, such as a gesture, is detected 604. Detection of the input triggers display of information for a second source, such as a second application. The second application may be any suitable application, such as described above. The information associated with the second application is also described above. The input may be considered to be a command associated with a second application, which command requests or causes at least some information associated with the second source or application to be displayed.


An appropriate input is advantageously assigned as the input such that unintentional display of information associated with the second source or application is avoided. Thus, the input, such as a gesture, is associated with the second source or application. The input may be associated with a specific location, such as a side or corner of the touch-sensitive display 118, or a displayed element, such as a special indicator, e.g., a ghosted symbol or word, or a header for an application, e.g., the header “FRIDAY May 7 10:50a” as shown in FIG. 7, and end of the displayed information associated with the first application, and so forth. The input may be a gesture having detectable attributes or characteristics, such as movement, direction, change in direction, shape, duration, length, force, speed, time associated with a given location as with a hover, number of simultaneous touch locations, number of taps, use in conjunction with a physical key, button, or other input device, and so forth. The input may be depression of a touch-sensitive display 118 that actuates an actuator 120, such as described above. The input may be provided while any end of the information associated with the first application is displayed. The input may be provided by selection from a menu. The input may be any combination of the above.


A few examples of an input are as follows. The input may be a gesture that extends substantially from one end of the display 118 to an opposite end of the display 118, such the swipe 804 shown in FIG. 8. The gesture may alternatively move across the narrow part of the display 118, e.g., at a right angle to the swipe 804 shown in FIG. 8. The input may be a hover or other gesture that remains associated with a specific location for a period of time, such as the sustained touch 904 at a location associated with a corner of the touch-sensitive display 118 where part of the header for the email application is displayed as shown in the example of FIG. 9. The input, such as a gesture, may be provided while any end of the information associated with the first application is displayed. The input may be associated with any end of the first information, such as the beginning of the information, the last part of the information, or a side of the information, such as the left side or right side of the displayed information, such as shown in FIG. 10. The input may be a compound gesture, for example, a touch sustained at a specific location, such as a corner or side of the display, while a swipe is detected. When the input is a gesture, the gesture need not be limited to a gesture input via an input device, e.g., a touch-sensitive display, optical joystick, and so forth, but may include other types of gestures such as 3D gestures or physical gestures involving movement of the electronic device 100.


Information associated with the second source, such as an application, referred to as second information, is displayed 606. The second information may be displayed at any end of the first information. For example, the second information may be displayed at the end of the first information that is displayed when the gesture is detected 604. In another example, the second information may be displayed at the end of the first information that is associated with the gesture, such as the left or right side of the display, such as shown in FIG. 10. The second information may be scrolled through after scrolling through the first information. For example, when a swipe begins on the display 118 and proceeds at least to any end of the display 118, the first information and the second information may be scrolled through substantially contiguously. Thus, both the first information and the second information may be displayed in a continuous stream of information, and information for two or more applications may be displayed at the same time. The second information may be displayed in any order, including chronological, reverse chronological, alphabetical, reverse alphabetical, most often accessed, and so forth. The information from two or more sources, such as applications, may be combined and displayed, rather than appending the information together.


The second information may be a preview of information, e.g., a subset of all the second information. For example, when the second application is email, the last five emails may be displayed, when the second application is an address book, the ten most often accessed contacts may be displayed, and so forth. The preview may be displayed without opening or launching the second application, in which case the previewed information may be retrieved from stored information and/or information received via a communication network 150. Alternatively, the second application may be launched or opened upon detection of the gesture.


The second information may continue 608 to be displayed, including scrolled through, as long as any second information remains on the display 112. For example, after all the second information has scrolled off the display 112, the first information, and not the second information, is displayed until a subsequent detection of an appropriate input, such as a gesture described above. In other words, when the input is not detected, scrolling through the first information stops when the end of the information is displayed, e.g., at an end of the display 112.


The second information may continue to be displayed for a predetermined time period, such as 5 or 10 seconds, which time period may be selected by a user and stored in a user profile. Second information may alternatively be discontinued 608 when an input, similar to or dissimilar to the gesture at 604, is detected. For example, if a clockwise circular gesture triggers display of the second information, a counter-clockwise circular gesture may discontinue display of the second information.


The present method may optionally be applied to two or more applications in addition to the first application. For example, once the second information is scrolled through, information associated with a third application may be displayed upon detection of an appropriate input, much the same way the second information is displayed when an input is detected during display of first information. Any number of applications may be displayed by repeating the process. For example, a long swipe during display of first information results in display of second information, and a second long swipe during display of the second information results is display of third information. Alternatively, a single input may display information from any number of sources or applications.


Alternatively, a different application may be associated with different ends of the information. For example, a gesture associated with the newest displayed emails may result in display of calendar information, a gesture associated with the oldest displayed emails may result in display of an address book, a gesture associated with the left side of the displayed emails may result in display of tasks, and a gesture associated with the right side of the displayed emails may result in display of media player controls.


A user profile may be utilized to store various options associated with the method, which options may be selected by a user. For example, a user may select which application opens when information for a given application is displayed. When multiple applications are opened or multiple sources of information are accessed, the order of the applications or sources may be stored. Applications associated with different ends of any source or application may be selected and stored. The input that triggers secondary source or application display may be selected and stored, for example, a hover, a swipe, a circle gesture, and so forth. A time duration for detection of a gesture may be stored in the profile. Time of display of the second information may be selected by the user and stored. How much information is displayed from a second source or application may be stored and selected, e.g., how many emails, contacts, logged phone calls, and so forth. When a second (which may be opened later than the first application) application is previewed or opened or launched. Options related to how the information is displayed may be included in the profile, including end-to-end display, combination of sources, order of combined sources such as chronological or time order, and so forth. Any other information related to the method may optionally be selected and stored in the user profile.


Examples of displaying information for a plurality of applications are shown in FIG. 7, FIG. 8, FIG. 9, FIG. 10, and FIG. 11. Although these examples show information displayed for an email application when the input is detected, any application may be displayed. While email application information 702 is displayed in FIG. 7, an input comprising a downward swipe 704 that begins at the end of the email information causes calendar information 706 to be displayed at that end of the email information.


While email application information 702 is displayed in FIG. 8, an input comprising an upward swipe 804 that begins at the bottom end of the touch-sensitive display 118 and ends at the opposite end of the touch-sensitive display 118 causes calendar information 806 to be displayed at that end of the email information, which is the bottom end of the email information in this example.


The method may be applied when information displayed in either portrait, such as shown in FIG. 7 and FIG. 8, or landscape orientations, such as shown in FIG. 9 and FIG. 10. While email application information 902 is displayed in FIG. 9, an input comprising a sustained touch 904, also referred to as a hover, is detected at a location associated with a corner of the display where a header for email information is displayed. Contact information 906 is displayed at that end of the email information.


While email application information 902 is displayed in FIG. 10, an input, such as a gesture associated with the right side of the display is detected, and contact information 1002 is displayed at right side of the display. FIG. 10 shows the transition from display of emails to display of contacts.


Alternatively, information may be displayed in a combined manner, such that information from two or more sources is combined and displayed. An example is shown in FIG. 11, which illustrates combination of information from four different sources, email, tasks, missed calls, and calendar. For example, in order to respond to John Roberts 10:45 AM email asking whether a user can meet at 3 PM, the user may need information from multiple sources, such as the calendar, task list, and missed calls, to answer the question. Existing portable devices typically require the user to separately open an application for each of these sources, requiring numerous steps and time.


As shown in FIG. 11, information associated with four sources or applications, email 1102, tasks 1104, missed calls 1104, and calendar 1108, is combined into a single list or grouping of information 1110 that is displayed. The portable electronic device 118 is shown in dashed lines to more clearly illustrate the list of information 1110. When the information 1110 is displayed in one window or field of the display 118, the list may advantageously be scrolled through. The list may be referred to as an extended list or extended message list. The information may optionally be combined according to a parameter, such chronological or time order, for further advantage, such as shown in FIG. 11. The user is provided with a combined list of information that is easily scrolled through to determine and answer to the question from John's email. Further, the user is provided with the ability to reply to the email from the same list of information. Optionally, the portable electronic device 100 need not launch or open the applications associated with the tasks, missed calls, or calendar. This information may be obtained, for example, from information stored on the portable electronic device 100.


Optionally, formatting of information on the extended list may be provided to provide more easily identifiable information. For example, different sources of information may have different formatting, such as italicizing, shading, highlighting, coloring, and so forth. For example, the missed calls and tasks are italicized in the extended list 1110 of FIG. 11. Dates may optionally be added to the list when information is associated with multiple dates. For example, May 8 is added to the appointments at the top of the list 1110 and May 6 is added to the missed call at the bottom of the list 1108. The current date and time may be displayed at a point in a chronological list where the current time and date fit chronologically, such as shown in FIG. 11. Display of current date and time more easily identifies the separation of past and future items in the list 1110.


A method comprises displaying in a window or field first information associated with a first source running on a portable electronic device, detecting an input to display second information associated with a second source, and displaying second information associated with the second source and the first information in the window or field.


A method comprises prior to detecting an input, displaying information from a first source in a window or field of a portable electronic device, detecting the input on the portable electronic device, subsequent to detecting the input, displaying information from two or more sources including the first source in the window or field. The information from the two or more sources may include information pertaining to at least one future event. The information from the two or more sources may be combined and displayed in chronological order. The input may be a gesture requesting display of at least some information associated with a source of information other than the first source.


Although a touch-sensitive display is described in the above examples as the input device for gestures, other touch-sensitive input devices, such as optical joysticks, optical trackpads, trackballs, other navigation devices, and so forth, may be utilized.


The present method and electronic device make opening or display of information associated with a second application quicker, because the user need not navigate to a home page or open multiple applications to view information from multiple sources, such as multiple applications. Further, the user need not switch between multiple applications and/or windows to perform a task, such as replying to an email with scheduling information or phone numbers, because all the information may be displayed, for example, in response to a simple gesture. Information related to both past information, such as emails and missed phone calls, and future events, such as calendar items or tasks, may be viewed in a single field or window without having to switch between windows or applications. All displayed information may be displayed chronologically or by another order among the information from at least two applications. Information from multiple sources may be scrolled through in a single list.


The present disclosure may be embodied in other specific forms without departing from its spirit or essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the disclosure is, therefore, indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims
  • 1. A method for temporarily viewing calendar information from within a display of message data in a messaging application on an electronic device, the method comprising: displaying, in a messaging application window generated by the messaging application, the message data including a list of messages in a chronological order and a header at a first end of the list of messages indicating a date associated with the first end of the list of messages;detecting a swipe gesture requesting combined temporary display of the message data and the calendar information, the swipe gesture starting on the header and swiping through at least a portion of the displayed list of messages;selecting the calendar information based on a chronological correlation between the calendar information and the date associated with the first end of the list of messages being displayed;appending, by the messaging application, the calendar information to the first end of the message data by maintaining at least some of the messages in the list of messages in the messaging application window and temporarily displaying the calendar information in a portion of the messaging application window, separated from the at least some of the messages by the header, wherein the combined display of the calendar information and the list of messages is scrollable as a single list; andonce the calendar information is scrolled off the display, removing the temporarily appended calendar information from the single list and scrolling through the message data without displaying the calendar information until a subsequent detection of the swipe gesture.
  • 2. The method of claim 1, wherein the calendar information is scrolled through after scrolling through the message data.
  • 3. The method of claim 1, wherein a calendar application is not launched upon detection of the gesture.
  • 4. A computer-readable device having computer-readable code executable by at least one processor of a portable electronic device to perform the method of claim 1.
  • 5. An electronic device to temporarily view calendar information from within a messaging application displaying message data on the electronic device, comprising: a display;a processor configured to: display, in a first messaging window generated by the messaging application on the display, the message data including a list of messages in a chronological order and a header at a first end of the list of messages indicating a date associated with the first end of the list of messages;detect, by the electronic device, a swipe gesture requesting combined temporary display of the message data and the calendar information, the swipe gesture starting on the header and swiping through at least a portion of the displayed list of messages;select the calendar information based on a chronological correlation between the calendar information and the date associated with the first end of the list of messages being displayed;temporarily append the calendar information to the first end of the message data by maintaining at least some of the messages in the list of messages in the messaging application window and temporarily displaying the calendar information in a portion of the messaging application window, separated from the at least some of the messages by the header, wherein the combined display of the calendar information and the list of messages is scrollable as a single list; andonce the calendar information is scrolled off the display, remove the temporarily appended calendar information from the single list and scroll through the message data without displaying the calendar information until a subsequent detection of the swipe gesture.
  • 6. A method for temporarily viewing calendar information from within a display of message data in a messaging application on an electronic device, the method comprising: displaying, in a first window generated by the messaging application, the message data including a list of messages in a chronological order and a header at a first end of the list of messages indicating a date associated with the first end of the list of messages;detecting a first input requesting display of the calendar information associated with a calendar application, the first input starting on the header and swiping through at least a portion of the displayed list of messages;selecting the calendar information based on a chronological correlation between the calendar information and the date associated with the first end of the list of messages being displayed;displaying, within the first window, the calendar information at the first end of the message data by maintaining at least some of the messages in the list of messages in the messaging application window and temporarily displaying the calendar information appended to the first end in a portion of the messaging application window, separated from the at least some of the messages by the header, wherein the combined display of the calendar information and the list of messages is scrollable as a single list; anddetecting a second input requesting display of third information associated with a third source;displaying, within the first window, the third information at the second end of the message data, such that the message data and the third information are displayed side-by-side;once the calendar information is scrolled out of the first window, removing the calendar information from the single list and scrolling through the message data without displaying the calendar information until a subsequent detection of the first input; andonce the third information is scrolled out of the first window, removing the third information from the second end of the message data and scrolling through the message data without displaying the third information until a subsequent detection of the second input.
  • 7. A computer-readable device having computer-readable code executable by at least one processor of a portable electronic device to perform the method of claim 6.
  • 8. A method for temporarily viewing calendar information from within a display of message data in a messaging application on an electronic device, the method comprising: displaying, in a window or field generated by the messaging application, the message data without displaying the calendar information, the message data including a list of messages in a chronological order and a header at a first end of the list of messages indicating a date associated with the first end of the list of messages;detecting, by the electronic device, an input to display the calendar information, the input starting on the header and swiping through at least a portion of the displayed list of messages;selecting the calendar information based on a chronological correlation between the calendar information and the date associated with the first end of the list of messages being displayed;temporarily appending, by the first application, the calendar information to the first end of the message data by maintaining at least some of the messages in the list of messages in the messaging application window and temporarily displaying the calendar information in a portion of the messaging application window, separated from the at least some of the messages by the header, wherein the combined display of the calendar information and the list of messages is scrollable as a single list without entering a menu and without selecting an icon associated with the calendar information; andonce the calendar information is scrolled out of the window or field, removing the calendar information from the single list and scrolling through the message data without displaying the calendar information until a subsequent detection of the input.
  • 9. A method for temporarily viewing calendar information from within a display of message data in a messaging application on an electronic device, the method comprising: prior to detecting an input, displaying, by the messaging application running on an electronic device, the message data in a window or field generated by the messaging application without displaying the calendar information in the window or field, the message data including a list of messages in a chronological order and a header at a first end of the list of messages indicating a date associated with the first end of the list of messages;detecting, by the electronic device, the input while the calendar information is not displayed, the input starting on the header and swiping through at least a portion of the displayed list of messages;in response to detecting the input: selecting the calendar information based on a chronological correlation between the calendar information and the date associated with the first end of the list of messages being displayed;temporarily appending the calendar information to the first end of the message data by maintaining at least some of the messages in the list of messages in the messaging application window and temporarily displaying the calendar information in a portion of the messaging application window, separated from the at least some of the messages by the header, wherein the combined display of the calendar information and the list of messages is scrollable as a single list without navigating to the second application; andonce the calendar information is scrolled out of the window or field, removing the calendar information from the single list and scrolling through the message data without displaying the calendar information until a subsequent detection of the input.
  • 10. The method of claim 9, wherein the single list includes information pertaining to at least one future event.
  • 11. The method of claim 9, wherein the single list is displayed in chronological order.
US Referenced Citations (275)
Number Name Date Kind
5305435 Bronson Apr 1994 A
5570109 Jenson Oct 1996 A
5651107 Frank et al. Jul 1997 A
5668960 Kataoka Sep 1997 A
6073109 Flores et al. Jun 2000 A
6133898 Ludolph et al. Oct 2000 A
6333973 Smith et al. Dec 2001 B1
6584181 Aktas et al. Jun 2003 B1
7079160 Colavin Jul 2006 B2
7190976 Enns Mar 2007 B2
7250955 Beeman et al. Jul 2007 B1
7283808 Castell et al. Oct 2007 B2
7308653 Lin-Hendel Dec 2007 B2
7370284 Andrea et al. May 2008 B2
7385875 May et al. Jun 2008 B2
7430409 Klassen et al. Sep 2008 B2
7484213 Mathew et al. Jan 2009 B2
7539945 Conrad et al. May 2009 B2
7642901 Kato et al. Jan 2010 B2
7647559 Yozell-Epstein et al. Jan 2010 B2
7752279 Hardy et al. Jul 2010 B2
7774418 Tang et al. Aug 2010 B2
7782307 Westerman et al. Aug 2010 B2
7802206 Davis et al. Sep 2010 B1
7809162 Steinberg et al. Oct 2010 B2
7812828 Westerman et al. Oct 2010 B2
7812860 King et al. Oct 2010 B2
7826641 Mandella et al. Nov 2010 B2
7844076 Corcoran et al. Nov 2010 B2
7844915 Platzer et al. Nov 2010 B2
7848549 Steinberg et al. Dec 2010 B2
7860274 Steinberg et al. Dec 2010 B2
7861169 Hull et al. Dec 2010 B2
7865562 Nesbitt Jan 2011 B2
7884846 Ferren et al. Feb 2011 B2
7899915 Reisman Mar 2011 B2
7900074 Reece et al. Mar 2011 B2
7904828 Conrad et al. Mar 2011 B2
7937672 Casto May 2011 B2
7996045 Bauer et al. Aug 2011 B1
8032482 Rosenberg et al. Oct 2011 B2
8032597 Khoo Oct 2011 B2
8082518 Flake et al. Dec 2011 B2
8099681 Flanagan et al. Jan 2012 B2
8122364 Yozell-Epstein et al. Feb 2012 B2
8134727 Shmunis et al. Mar 2012 B1
8140115 Kahn et al. Mar 2012 B1
8140975 Lemay et al. Mar 2012 B2
8176411 Palmieri May 2012 B2
8205234 Eguchi Jun 2012 B1
8224391 Kim et al. Jul 2012 B2
8237664 Swanbufg et al. Aug 2012 B2
8239785 Hinckley et al. Aug 2012 B2
8249664 Bauer et al. Aug 2012 B1
8253695 Ganatra et al. Aug 2012 B2
8261213 Hinckley et al. Sep 2012 B2
8271660 Schulzrinne et al. Sep 2012 B2
8271907 Kim et al. Sep 2012 B2
8280962 Muniz et al. Oct 2012 B2
8291344 Chaudhri Oct 2012 B2
8296332 Boley et al. Oct 2012 B2
8300005 Tateuchi et al. Oct 2012 B2
8301701 Goodman et al. Oct 2012 B2
8356256 Olsen Jan 2013 B2
8359017 Bruchelt Jan 2013 B2
8359335 Coker et al. Jan 2013 B2
8392837 Li Mar 2013 B2
8402384 Scott Mar 2013 B2
8453057 Stallings et al. May 2013 B2
8473843 Lundy et al. Jun 2013 B2
8473870 Hinckley et al. Jun 2013 B2
8479122 Hotelling et al. Jul 2013 B2
8510677 van Os Aug 2013 B2
8539384 Hinckley et al. Sep 2013 B2
8650501 Arnold et al. Feb 2014 B2
8681112 Singhal Mar 2014 B2
8689146 Lazaridis et al. Apr 2014 B2
8711416 Byer et al. Apr 2014 B1
8726198 Rydenhag et al. May 2014 B2
8745141 Rosenberg et al. Jun 2014 B2
8756257 Szyperski et al. Jun 2014 B2
8996996 Agarwal et al. Mar 2015 B2
20010028365 Ludolph Oct 2001 A1
20020098831 Castell et al. Jul 2002 A1
20020126155 Lin-Hendel Sep 2002 A1
20030070000 Coker et al. Apr 2003 A1
20040068545 Daniell et al. Apr 2004 A1
20040117451 Chung Jun 2004 A1
20040128353 Goodman et al. Jul 2004 A1
20040196259 Bradski Oct 2004 A1
20040243677 Curbow et al. Dec 2004 A1
20050001848 Colavin Jan 2005 A1
20050108655 Andrea et al. May 2005 A1
20060026521 Hotelling et al. Feb 2006 A1
20060075046 Yozell-Epstein et al. Apr 2006 A1
20060101350 Scott May 2006 A1
20060123360 Anwar et al. Jun 2006 A1
20060156240 Lemay et al. Jul 2006 A1
20060190833 SanGiovanni et al. Aug 2006 A1
20060250377 Zadesky et al. Nov 2006 A1
20060256082 Cho et al. Nov 2006 A1
20060270461 Won et al. Nov 2006 A1
20060284852 Hofmeister et al. Dec 2006 A1
20070011258 Khoo Jan 2007 A1
20070016958 Bodepudi et al. Jan 2007 A1
20070038718 Khoo et al. Feb 2007 A1
20070083600 Bakos et al. Apr 2007 A1
20070106939 Qassoudi May 2007 A1
20070139372 Swanburg et al. Jun 2007 A1
20070150842 Chaudhri et al. Jun 2007 A1
20070152977 Ng et al. Jul 2007 A1
20070220444 Sunday et al. Sep 2007 A1
20070236468 Tuli Oct 2007 A1
20070240042 Sato Oct 2007 A1
20070256035 Matsuzawa et al. Nov 2007 A1
20070271376 Yach Nov 2007 A1
20080005247 Khoo Jan 2008 A9
20080008163 Castell et al. Jan 2008 A1
20080034047 Rosenberg et al. Feb 2008 A1
20080034381 Jalon et al. Feb 2008 A1
20080046824 Li et al. Feb 2008 A1
20080065758 Narayanaswami Mar 2008 A1
20080094369 Ganatra et al. Apr 2008 A1
20080165151 Lemay et al. Jul 2008 A1
20080165160 Kocienda Jul 2008 A1
20080174570 Jobs et al. Jul 2008 A1
20080189622 Sanchez et al. Aug 2008 A1
20080220747 Ashkenazi et al. Sep 2008 A1
20080231601 Fyke et al. Sep 2008 A1
20080261569 Britt et al. Oct 2008 A1
20080272927 Woolley et al. Nov 2008 A1
20080273014 Lowles et al. Nov 2008 A1
20090006991 Lindberg et al. Jan 2009 A1
20090007017 Anzures Jan 2009 A1
20090013282 Mercer Jan 2009 A1
20090049407 Casto Feb 2009 A1
20090064055 Chaudhri et al. Mar 2009 A1
20090094562 Jeong et al. Apr 2009 A1
20090119678 Shih et al. May 2009 A1
20090144661 Nakajima et al. Jun 2009 A1
20090174679 Westerman Jul 2009 A1
20090177754 Brezina et al. Jul 2009 A1
20090178006 Lemay et al. Jul 2009 A1
20090195518 Mattice et al. Aug 2009 A1
20090199130 Tsern et al. Aug 2009 A1
20090201316 Bhatt Aug 2009 A1
20090210946 Cohen Aug 2009 A1
20090237367 Ryu et al. Sep 2009 A1
20090241072 Chaudhri et al. Sep 2009 A1
20090249247 Tseng et al. Oct 2009 A1
20090252312 Muniz Oct 2009 A1
20090267909 Chen et al. Oct 2009 A1
20090273583 Norhammar Nov 2009 A1
20090278806 Duarte et al. Nov 2009 A1
20090292690 Culbert Nov 2009 A1
20090295753 King et al. Dec 2009 A1
20090307622 Jalon et al. Dec 2009 A1
20090307626 Jalon et al. Dec 2009 A1
20090307631 Kim et al. Dec 2009 A1
20090307710 Zarzychi et al. Dec 2009 A1
20100011304 Van Os Jan 2010 A1
20100013782 Liu et al. Jan 2010 A1
20100017695 Palmieri Jan 2010 A1
20100042954 Rosenblatt et al. Feb 2010 A1
20100050076 Roth Feb 2010 A1
20100058226 Flake et al. Mar 2010 A1
20100060586 Pisula et al. Mar 2010 A1
20100066698 Seo Mar 2010 A1
20100079392 Chiang et al. Apr 2010 A1
20100095224 Yozell-Epstein et al. Apr 2010 A1
20100095239 McCommons et al. Apr 2010 A1
20100107067 Vaisanen et al. Apr 2010 A1
20100153951 Jones Jun 2010 A1
20100156656 Duarte et al. Jun 2010 A1
20100162180 Dunnam Jun 2010 A1
20100169722 Wu et al. Jul 2010 A1
20100171753 Kwon Jul 2010 A1
20100175018 Petschnigg et al. Jul 2010 A1
20100178024 Agarwal et al. Jul 2010 A1
20100182248 Chun Jul 2010 A1
20100185989 Shiplacoff et al. Jul 2010 A1
20100211535 Rosenberger Aug 2010 A1
20100214234 Singhal Aug 2010 A1
20100214237 Echeverri et al. Aug 2010 A1
20100218130 Conrad et al. Aug 2010 A1
20100231533 Chaudhri Sep 2010 A1
20100235794 Ording Sep 2010 A1
20100248689 Teng et al. Sep 2010 A1
20100251178 Lee et al. Sep 2010 A1
20100289760 Jonoshita et al. Nov 2010 A1
20100295772 Alameh et al. Nov 2010 A1
20100302172 Wilairat Dec 2010 A1
20100306693 Brinda Dec 2010 A1
20100306705 Nilsson Dec 2010 A1
20100317408 Ferren et al. Dec 2010 A1
20110029927 Lietzke et al. Feb 2011 A1
20110034208 Gu et al. Feb 2011 A1
20110061021 Kang et al. Mar 2011 A1
20110083111 Forutanpour et al. Apr 2011 A1
20110099490 Barraclough et al. Apr 2011 A1
20110112771 French May 2011 A1
20110163944 Bilbrey et al. Jul 2011 A1
20110163970 Lemay Jul 2011 A1
20110163989 Singhal Jul 2011 A1
20110167369 van Os Jul 2011 A1
20110175748 Small et al. Jul 2011 A1
20110175839 Prabhu Jul 2011 A1
20110181526 Shaffer et al. Jul 2011 A1
20110185318 Hinckley et al. Jul 2011 A1
20110209088 Hinckley et al. Aug 2011 A1
20110209097 Hinckley et al. Aug 2011 A1
20110209104 Hinckley et al. Aug 2011 A1
20110210983 Theimer et al. Sep 2011 A1
20110231499 Stovicek et al. Sep 2011 A1
20110252369 Chaudhri Oct 2011 A1
20110252381 Chaudhri Oct 2011 A1
20110256848 Bok et al. Oct 2011 A1
20110294467 Kim et al. Dec 2011 A1
20120026194 Wagner et al. Feb 2012 A1
20120032979 Blow et al. Feb 2012 A1
20120069131 Abelow Mar 2012 A1
20120083260 Arriola et al. Apr 2012 A1
20120084697 Reeves Apr 2012 A1
20120084698 Sirpal et al. Apr 2012 A1
20120084713 Desai et al. Apr 2012 A1
20120090004 Jeong Apr 2012 A1
20120102437 Worley et al. Apr 2012 A1
20120105358 Momeyer et al. May 2012 A1
20120110087 Culver et al. May 2012 A1
20120115449 Bruchelt May 2012 A1
20120154303 Lazaridis et al. Jun 2012 A1
20120159380 Kocienda et al. Jun 2012 A1
20120173993 Chakra et al. Jul 2012 A1
20120180001 Griffin et al. Jul 2012 A1
20120192108 Kolb Jul 2012 A1
20120206392 Ng et al. Aug 2012 A1
20120210214 Yoo et al. Aug 2012 A1
20120226978 Harberts et al. Sep 2012 A1
20120235930 Lazaridis et al. Sep 2012 A1
20120236037 Lessing et al. Sep 2012 A1
20120266082 Webber Oct 2012 A1
20120280917 Toksvig et al. Nov 2012 A1
20120284673 Lamb et al. Nov 2012 A1
20120290946 Schrock et al. Nov 2012 A1
20120304107 Nan et al. Nov 2012 A1
20120304108 Jarrett Nov 2012 A1
20120311444 Chaudhri Dec 2012 A1
20120326984 Ghassabian Dec 2012 A1
20130002524 Sirpal et al. Jan 2013 A1
20130007665 Chaudhri et al. Jan 2013 A1
20130024820 Kirkpatrick Jan 2013 A1
20130031515 Funabashi et al. Jan 2013 A1
20130033477 Sirpal et al. Feb 2013 A1
20130055170 Langlois et al. Feb 2013 A1
20130063383 Anderssonreimer et al. Mar 2013 A1
20130083260 Minami Apr 2013 A1
20130117689 Lessing et al. May 2013 A1
20130117718 Lazaridis et al. May 2013 A1
20130141371 Hallford et al. Jun 2013 A1
20130145295 Bocking et al. Jun 2013 A1
20130159941 Langlois et al. Jun 2013 A1
20130167066 Scott Jun 2013 A1
20130185650 Gutowitz Jul 2013 A1
20130187863 Rydenhag et al. Jul 2013 A1
20130187869 Rydenhag et al. Jul 2013 A1
20130191791 Rydenhag et al. Jul 2013 A1
20130321340 Seo et al. Dec 2013 A1
20130326401 van Os Dec 2013 A1
20130332886 Cranfill et al. Dec 2013 A1
20140011485 Forstall et al. Jan 2014 A1
20140109020 Wielgosz Apr 2014 A1
20140111440 Garside et al. Apr 2014 A1
20140304657 Biswas Oct 2014 A1
20160366078 Razavian Dec 2016 A1
20160366079 Razavian Dec 2016 A1
Foreign Referenced Citations (23)
Number Date Country
1834887 Sep 2006 CN
101692194 Apr 2010 CN
2015176 Jan 2009 EP
2045700 Apr 2009 EP
2045700 Apr 2009 EP
2068236 Jun 2009 EP
2068236 Jun 2009 EP
2109030 Oct 2009 EP
2383636 Nov 2011 EP
2458493 May 2012 EP
2485138 Aug 2012 EP
10-2008-0041809 May 2008 KR
10-2009-0036578 Apr 2009 KR
10-2010-0032660 Mar 2010 KR
20100023637 Mar 2010 KR
201118666 Jun 2011 TW
2004051451 Jun 2004 WO
2009097555 Aug 2009 WO
2009120925 Oct 2009 WO
2010040670 Apr 2010 WO
2010110613 Sep 2010 WO
2012097385 Jul 2012 WO
2012128795 Sep 2012 WO
Non-Patent Literature Citations (21)
Entry
Extended European Search Report for EP Application No. 11156282.3, dated Jul. 27, 2011, 7 pages.
Office Action for related U.S. Appl. No. 13/607,330, dated Jan. 22, 2013, 27 pages.
http://www.evernote.com/peek/ Retrieved Aug. 27, 2012, 2 pages.
http://www.jimblackler.net/blog/?p=67/ “QuickCalendar, an application for Android written in Java” Retrieved Oct. 18, 2012, 6 pages.
http://www.support.apple.com/kb/HT3756/ “iOS: Understanding Notifications” Retrieved Oct. 18, 2012, 3 pages.
International Searching Authority, International Search Report and Written Opinion, issued for PCT/US2012/026970, mailed on Oct. 4, 2012, 10 pages.
Android Users Guide 2.3 (Google, Inc.) Dec. 13, 2010, see pp. 29-30, pp. 380. (English).
Android Users Guide 2.3 (Google, Inc.) Dec. 13, 2010, see pp. 27-28, pp. 368. (Korean).
“User Guide” Samsung Epic 4G, A Galaxy S Phone, Sprint Oct. 8, 2010, pp. 268.
Korean Office Action dated Jun. 20, 2013, issued in counterpart Korean Application No. 10-2012-0016518, 6 pages.
United States Patent and Trademark Office, “Notice of Allowance,” issued is U.S. Appl. No. 13/607,330, mailed Nov. 7, 2013, 34 pages.
http://www.gigaom.com/2011/10/12/ios-5-notifications-and-notification-center/, Retrieved May 2, 2013, Asch, Josh, “iOS 5: Notifications and Notification Center”, Tech News and Analysis, Oct. 12, 2011, four pages.
Office Action in related U.S. Appl. No. 13/607,330 issued Aug. 27, 2013, 34 pages.
Microsoft, “Cross Sliding State enumeration”, internet article, http://msdn.microsoft.com.en-us/library/windows/apps/windows.ui.inout.crosslidingstate, retrieved Sep. 4, 2012, 3 pages.
Levesque et al., Frictional Widgets: Enhancing Touch Interfaces with Programmable Friction, published CHI 2011, ACM 978-1-4503-0268-5/11/05, May 7-12, 2011, 6 pages.
Canadian Intellectual Property Office, Office Action issued in connection with Canadian Application No. 2,768,287, dated Jan. 10, 2014, pp. 3.
Canadian Intellectual Property Office, Office Action issued in connection with Canadian Application No. 2,768,287, dated Oct. 14, 2014, 4 pages.
Office Action issued in Canadian Application No. 2,768,287 on Jul. 3, 2015; 7 pages.
Communication Pursuant to Article 94(3) EPC issued in EP Application No. 11156282.3 on Dec. 22, 2014; 8 pages.
Office Action issued in Chinese Application No. 201210043818.2 on Mar. 25, 2015; 7 pages.
Office Action issued in Canadian Application No. 2,768,287 on May 30, 2016; 4 pages.
Related Publications (1)
Number Date Country
20120218192 A1 Aug 2012 US