The following description relates generally to providing an instant messaging interface having a tear-off element.
Online service providers facilitate access to information and services by providing interactive UIs (User Interfaces) that help users navigate to desired resources. Generally, a UI allows a user to execute particular commands or to link to certain locations by simply selecting screen objects such as icons, windows, and drop-down menus. The design of a UI has a significant impact on a user's online experience. In particular, the icons, the windows, and the menus of a UI may be arranged to enable a user to locate preferred information and services quickly and easily.
In one general aspect, a user interface on a display enables user perception of information regarding a communications session that leverages an instant messaging platform. The user interface includes an instant messaging application user interface and one or more tear-off elements corresponding to ongoing instant messaging communications sessions. Each tear-off element is configured to enable perception and selection by a user of a corresponding instant messaging communications session. Also, each tear-off element is configured to be independently visually separated from other elements of the instant messaging application user interface and maintained as a separate entity on the instant messaging application user interface.
Implementations may include one or more of the following features. For example, the instant messaging application user interface may include a general interface tear-off element that is configured to enable perception and selection of several of the tear-off elements collectively and to enable collective visual separation of the several tear-off elements from other elements of the instant messaging application user interface. The general interface tear-off element may be, for example, a tab or a button. The interface may be configured to enable reattachment to other elements of the general interface. For instance, a tear-off element may be configured to be reattached to an interface other than the interface from which the tear-off element was separated.
In one implementation, one or more tear-off elements may be dedicated to and enable perception and selection of a single corresponding instant messaging communications session. The dedicated tear-off elements may be independently visually separable from other elements of the instant messaging application user interface. The dedicated tear-off elements may include, for example, tabs or buttons. The user interface may also include a manual status control associated with a dedicated tear-off element. For instance, the manual status control may enable an indication of whether a message in the corresponding instant messaging communications session has been perceived by the user.
In one implementation, one or more of the tear-off elements may be rendered visually as an integral part of the instant messaging application user interface. In another implementation, the display of the tear-off element persists when the element is visually separated from other elements of the instant messaging application user interface. In yet another implementation, the tear-off element may be configured to enable reattachment to other elements of the instant messaging application user interface.
The tear-off elements may be configured to be separately manipulable. In one implementation, one or more of the tear-off elements may be configured to be separately removable from the instant messaging application user interface, separately invokable, separately minimizable and/or separately movable.
In one implementation, more than one of the tear-off elements may be configured to be collectively visually separated from other elements of the instant messaging application user interface and maintained as a separate display element. In another implementation, a tear-off element may configured to be individually visually separated from other elements of the instant messaging application user interface and maintained as a separate display element. In yet another implementation, the instant messaging application user interface and tear-off elements may be configured to display limited information about one or more concurrent instant messaging sessions. For instance, the user interface may enable a more detailed display of one or more of the instant messaging sessions through selection of a corresponding tear-off element.
Aspects of the instant messaging interface having a tear-off element may be implemented by an apparatus and/or by a computer program stored on a computer readable medium. The computer readable medium may comprise a disc, a client device, a host device, and/or a propagated signal. In addition, aspects of the instant messaging interface having a tear-off element may be implemented in a client/host context or in a standalone or offline client device. The instant messaging interface having a tear-off element may be rendered in a client/host context and may be accessed or updated through a remote device in a client/host environment. The instant messaging interface having a tear-off element also may be rendered by the standalone/offline device and may be accessed or updated through a remote device in a non-client/host environment such as, for example, a LAN server serving an end user or a mainframe serving a terminal device.
Other features will be apparent from the following description, including the drawings, and from the claims.
Like reference symbols in the various drawings indicate like elements.
In general, one or more tear-off elements may be provided in an interface for instant messaging (IM) applications or other online applications. For example, tear-off elements may be provided to collectively form a tabbed IM user interface (UI), where each tear-off element represents a corresponding ongoing IM session. A user may tear-off one or more of the tear-off elements individually or collectively. Tear-off elements that have been torn off may be independently or collectively reattached to the user interface from which they were torn, or they may be reattached to a different user interface. In addition, once torn, the tear-off elements may be separately or collectively manipulated, moved, minimized, invoked, and activated.
In the example of a tabbed IM UI, the tear-off elements may be presented as tabs positioned adjacent to one another to enable selection of and switching between IM sessions, and other operations. When several tear-off element tabs are concurrently shown, an active tab corresponds to the IM session currently being viewed or manipulated by the user, and inactive tabs correspond to the IM sessions which are not currently being viewed or manipulated by the user. A tear-off element tab typically includes an identifier, such as the screen name of an IM buddy, to identify the particular IM session to which the tab is assigned. When displayed, the identifier for an IM session typically is configured such that a user is able to read or otherwise recognize the identifier without additional information. A tear-off element tab also may include a status indicator to indicate whether a new IM message is waiting to be viewed in the IM session corresponding to that tear-off element tab.
A tear-off element may be rendered by any type of hardware, software, device, computer, computer system, equipment, component, program, application, code, storage medium, or propagated signal. In one implementation, the tear-off element is rendered in a client/host context, and the tear-off element may be accessed or updated through a remote device in a client/host environment. In another implementation, the tear-off element is implemented in a standalone or offline client context, where the tear-off element is rendered by the standalone/offline device and accessed or updated through a remote device in a non-client/host environment such as, for example, a LAN server serving an end user or a mainframe serving a terminal device.
Typically, IM communications involve an instantaneous or nearly instantaneous communication between two users, where each user is able to perceive online presence information regarding other selected users (“buddies”). The IM communications may be machine-to-machine communications that occur without intervention by, or communication through, an instant messaging server after a communication session is established or authentication is performed. Examples of IM communications include those provided by AIM (America Online Instant Messenger), AOL (America Online) Instant Messaging, Yahoo Messenger, MSN Messenger, and ICQ, among others. Although discussed below primarily with respect to IM applications, the tear-off element may be provided for other online applications such as chat, e-mail, and players for streaming media.
For illustrative purposes,
The client device 120 typically includes a general-purpose computer 170 having an internal or external memory 172 for storing data and programs such as an operating system 174 (e.g., DOS, Windows™, Windows 95™, Windows 98™, Windows 2000™, Windows Me™, Windows XP™, Windows NT™, OS/2, or Linux) and one or more application programs. Examples of application programs include authoring applications 176 (e.g., word processing programs, database programs, spreadsheet programs, or graphics programs) capable of generating documents or other electronic content; client applications 178 (e.g., America Online (AOL) client, CompuServe client, AOL Instant Messenger (AIM) client, interactive television (ITV) client, Internet Service Provider (ISP) client, or instant messaging (IM) client) capable of communicating with other computer users, accessing various computer resources, and viewing, creating, or otherwise manipulating electronic content; and browser applications 180 (e.g., Netscape's Navigator or Microsoft's Internet Explorer) capable of rendering standard Internet content and other content formatted according to standard protocols such as the Hypertext Transfer Protocol (HTTP).
One or more of the application programs may be installed on the internal or external storage 172 of the general-purpose computer 170. Alternatively, in another implementation, the client controller 125 may access application programs externally stored in and/or performed by one or more device(s) external to the general-purpose computer 170.
The general-purpose computer 170 also includes a central processing unit 182 (CPU) for executing instructions in response to commands from the client controller 125, and a communication device 184 for sending and receiving data. One example of the communication device 184 is a modem. Other examples include a transceiver, a set-top box, a communication card, a satellite dish, an antenna, a network adapter, or some other mechanism capable of transmitting and receiving data over the communications link 115 through a wired or wireless data pathway 150. The general-purpose computer 170 optionally includes a television (“TV”) tuner 186 for receiving television programming in the form of broadcast, satellite, and/or cable TV signals. The TV tuner 186 permits the client device 120 to selectively and/or simultaneously display network content received by communications device 184 and TV programming content received by the TV tuner 186.
The general-purpose computer 170 may include an input/output interface 188 that enables wired or wireless connection to various peripheral devices 190. Examples of peripheral devices 190 include, but are not limited to, a mouse 191, a mobile phone 192, a personal digital assistant 193 (PDA), an MP3 player (not shown), a keyboard 194, a display monitor 195 with or without a touch screen input, a TV remote control 196 for receiving information from and rendering information to users, and an audiovisual input device 198.
Although
Referring to
The client device 120 and the host device 135 are generally capable of executing instructions under the command of, respectively, a client controller 125 and a host controller 140. The client device 120 and the host device 135 are connected to, respectively, the client controller 125 and the host controller 140 by, respectively wired or wireless data pathways 130 and 145, which are capable of delivering data.
The client device 120, the client controller 125, the host device 135, and the host controller 140 typically each include one or more hardware components and/or software components. An example of a client device 120 or a host device 135 is a general-purpose computer (e.g., a personal computer) or software on such a computer capable of responding to and executing instructions in a defined manner. Other examples include a special-purpose computer, a workstation, a server, a device, a component, other physical or virtual equipment or some combination of these capable of responding to and executing instructions. The client device 120 and the host device 135 may include devices that are capable of establishing peer-to-peer communications.
An example of client controller 125 or host controller 140 is a software application loaded on the client device 120 or the host device 135 for commanding and directing communications enabled by the client device 120 or the host device 135. Other examples include a program, a piece of code, an instruction, a device, a computer, a computer system, or a combination of these for independently or collectively instructing the client device 120 or the host device 135 to interact and operate as described. The client controller 125 and the host controller 140 may be embodied permanently or temporarily in any type of machine, component, physical or virtual equipment, storage medium, or propagated signal capable of providing instructions to the client device 120 and the host device 135.
The communications link 115 typically includes a delivery network 160 making a direct or indirect communication between the client system 105 and the host system 110, irrespective of physical separation. Examples of a delivery network 160 include the Internet, the World Wide Web, WANs, LANs, analog or digital wired and wireless telephone networks (e.g. Public Switched Telephone Network (PSTN), Integrated Services Digital Network (ISDN), and Digital Subscriber Line (xDSL)), radio, television, cable, or satellite systems, and other delivery mechanisms for carrying data. The communications link 115 may include communication pathways 150, 155 that enable communications through the one or more delivery networks 160 described above. Each of the communication pathways 150, 155 may include, for example, a wired, wireless, cable or satellite communication pathway.
In one implementation, the IM host system 310 may have characteristics similar to those described above with respect to host system 110, and the client system 105 and the buddy client system 305 may include communication software to enable users of the client systems to the IM host system 310.
The IM host system 310 may support IM services irrespective of a user's network or Internet access. Thus, the IM host system 310 may allow users to send and receive IMs, regardless of whether they have access to any particular ISP. The IM host system 310 also may support associated services, such as administrative matters, advertising, directory services, chat, and interest groups related to the IM. The IM host system 310 has an architecture that enables the devices (e.g., servers) within the IM host system 310 to communicate with each other. To transfer data, the IM host system 310 employs one or more standard or exclusive IM protocols.
To access the IM host system 310 to begin an IM session in the implementation of
Once connectivity is established, a user who is using client system 105 may view whether a buddy using buddy client system 305 is online, and typically may view whether the buddy is able to receive IMs. If the buddy is online, the user may exchange IMs with that buddy.
In one implementation, the IMs sent between client system 105 and buddy client system 305 are routed through IM host system 310. In another implementation, the IMs sent between client system 105 and buddy client system 305 are routed through a third party server (not shown), and also may or may not be routed through IM host system 310. In yet another implementation, the IMs are sent directly between client system 105 and buddy client system 305.
Referring to
Procedure 400 generally involves rendering a tear-off element for instant messaging (IM) applications or other online applications. While some functions of procedure 400 may be performed entirely by the client system 105, other functions may be performed by the collective operation of the client system 105 and the IM host system 310. For example, a tear-off element may be rendered entirely by the client. However, the UI may be rendered based upon information provided to the client by the IM host system.
In procedure 400, a general client UI, including an IM UI and a general interface tear-off element, is rendered (step 405). For example,
The IM interface 525 is a tabbed IM interface. IM interface 525 includes sub-interfaces 526 that each have an associated sub-interface actionable item (tear-off element) 522 and represent a distinct and concurrent ongoing communications session. The tear-off element may include, for example, a button or a tab. The tear-off element 522 enables the activation and deactivation of the corresponding sub-interface 526 and, consequently, enables or disables user perception of the ongoing communications session. In the example of
The tear-off element 522 persists beyond active display of the associated sub-interface 526. The element 522 identifies the communications session, and allows the user to activate the sub-interface 526 if not currently displayed. For example, the tear-off element 522c persists beyond active display of the associated sub-interface 526c, identifies the communications session, and allows the user to activate the sub-interface 526c if not currently displayed. Also, each of the tear-off elements 522a, 522b, and 522d persists beyond active display of their associated sub-interfaces (not shown), identifies each communications session, and allows the user to activate the sub-interface that is not currently displayed. However, if the IM interface 525 is closed, minimized, or otherwise removed from active display, the associated tear-off elements 522a, 522b, 522c, 522d are likewise closed, minimized, or otherwise removed from active display unless the tear-off element 522 has been “torn off.” A tear-off element that has been torn off persists beyond active display of the associated interface 525 and the associated sub-interface 526. The torn off sub-interface may be reattached by the user, and will no longer persist beyond active display of the associated interface once it has been reattached. Also, in one implementation, the general interface tab 520 may be a tear-off tab, and may enable IM interface 525 may to be torn off from the toolbar 505, and persist even after the user navigates to and displays a different interface. For example, the IM interface 525 and the corresponding general interface tear-off tab 520 may be torn off and persist in display while the user navigates to and displays a different interface, such as an interface for writing e-mail. In the example of
Referring again to
Next, the IM host system 310 provides an IM message from a first IM buddy to the client system 105 (step 415). The IM host system 310 may provide the IM message across a network 160, and the IM message may include a text message portion, a time of delivery, and a screen name of the first IM buddy.
Referring also to
The IM UI includes a first tear-off element corresponding to the IM session with the first buddy, and also may include other actionable items corresponding to other IM sessions with other buddies. For example, as shown in
Rendering the first tear-off element also may include initializing or updating the status indicator, the identifier, the conversation counter, the display area status indicator, the information indicator, and the display area. Also, if the maximum number of concurrent IM sessions or tear-off elements corresponding to IM sessions available for display is exceeded when the IM message is provided, then rendering the tabbed IM UI may include rendering a scroll arrow, examples of which are described with respect to
The UI 600 includes an IM interface 525, and the IM interface 525 includes an IM display area 605 to display the IM conversation 526c1 of an IM session being actively displayed and represented by sub-interface 526c and tear-off element 522c. An IM compose area 610 is used to compose a message to send to the IM buddy (“ChattingChuck”) in the active IM session, typically by clicking on the send control button 615 in the UI. Font and appearance controls 612 are provided to control how the message being entered in the IM compose area 610 is displayed to the IM buddy and in the IM display area 605 once the message in the IM compose area 610 is sent. A control button 617 is provided to close the active IM session. The IM conversation 526c1 may include the identity of an IM buddy along with a message from that buddy, and also may include other information such as the time that a message was sent or received.
The IM interface 525 of UI 600 contains tear-off elements 522 and 622. Each of tear-off elements 522 and 622 is associated with a sub-interface 526 and assigned to a pending IM session. The instant messaging session may use a combination of text, graphics, audio, and video data to communicate with an IM buddy. The IM buddy may be identified by a screen name and typically is another user or an automated system, such as an artificial intelligence system or other automated system or agent having a screen name that responds to IM queries from a user. An active tear-off element 522c corresponds to the IM session that the user views or with which the user interacts currently through, for example, sub-interface 526c. Inactive tear-off elements 522a, 522b, 522d, and 622e through 622j correspond to the other concurrent IM sessions that the user currently does not fully view or with which the user currently is not enabled to interact. The user ordinarily is not able to perceive the conversations or a portion of the conversations in the communications sessions corresponding to the inactive tear-off elements. Also, the user ordinarily is not able to perceive any of the IM conversations if the IM interface 525 is no longer actively displayed.
An area 623 is provided to display various icons and controls. For example, the area 623 may include a buddy icon 623a corresponding to the IM buddy from whom an IM message was received, and a buddy icon 623e corresponding to the user who has received and is viewing the IM message. Other controls are provided, including a control 623b to retrieve information about the IM buddy, a control 623c to notify the service provider of inappropriate behavior by the IM buddy, a control 623d to indicate to the user whether the IM buddy is using a mobile device, a control 623f to setup various features of the service, and a control 623g to invite a new buddy to join in the IM session, among others. Also, a control button 630 is provided to initiate a new IM session with a different IM buddy.
The IM interface 525 of UI 600 includes a conversation counter 650 that provides information relating to the concurrent IM sessions, such as the total number of concurrent IM sessions, the number of new IM sessions, and the number of ongoing IM sessions having a new IM message waiting to be viewed. In general, the conversation counter 650 provides a perceivable indication to the user of statistics regarding the concurrent instant messaging session. In the example of
The scroll bars 643 and 645 allow the user to scroll up and down among the concurrent IM sessions, and provide an indication that one or more of the IM sessions “hidden” by the scroll bar has a new IM message waiting to be viewed. For example, as shown in
The tear-off elements 522 and 622 include a status indicator (e.g., 622a2, 622b2, 622d2, 622h2) to indicate whether a new IM message within the IM session corresponding to an interface tear-off element remains pending for review. In general, the indicator provides a perceivable status indication to the user that a new message is pending in at least one concurrent instant messaging session. Once the new message is viewed or acknowledged, the indicator changes and the conversation counter 650 is updated to reflect one fewer message waiting to be viewed. The tear-off elements 522 and 622 also may include an identifier, such as the screen name of the IM buddy, to identify the particular IM session to which it is assigned. Although not shown in
The IM interface 525 of UI 600 also includes a manual status control 655 to enable the user to manually indicate whether the last message from the IM buddy corresponding to the IM session for the active tear-off element displayed in the IM display area 605 has been viewed or acknowledged, without having to send an actual reply message to extinguish the new message status. The IM interface 525 of UI 600 also includes a last message information indicator 660 that provides information about the time that the last message was received from an IM buddy.
Referring again to
The IM Host system 310 provides the IM message to the first IM buddy (step 425). The IM host system 310 may provide the IM message across a network 160 to the client system associated with the first buddy (not shown).
Next, the client system 105 renders a second tear-off element for the IM interface (step 430). The second tear-off element corresponds to a second IM session from a second buddy. If the second IM session is to be actively displayed, a second sub-interface 526 associated with the second tear-off element 522 is rendered. In one implementation, the client system 105 renders the second tear-off element 522 when the IM message from the second IM buddy is provided and separately renders other portions of the IM user interface 525 at a different time. In another implementation, the entire IM user interface 525, including the second tear-off element 522 and second sub-interface 526, is rendered when the second IM message is provided. For example, as shown below with respect to
Rendering second tear-off element also may include updating the status indicator, the conversation counter, the display area status indicator, the information indicator, and the display area. For example, referring to
Referring again to
Referring again to
The user then performs a tear off of the second tear-off element and the sub-interface (step 445). As discussed below with respect to
As shown in
Other implementations are possible for performing the tear off of step 445. For example, as shown in
In one implementation, the windowing item 1205 may be configured to allow the user to select between performing successive tear-offs or successive reattachments. In other implementations, the windowing item 1205 may be configured such that successive actuations of the windowing item 1205 toggle between performing a tear off and performing a reattachment.
Next, the user reattaches the IM general interface tear-off element (step 450). As discussed below with respect to
The user then navigates to different functionality, and an updated UI is rendered (step 455). For example, as shown below with respect to
Referring to
Next, the user navigates to the IM interface and reattaches the second tear-off element (step 460). For example, as shown in
Other implementations are possible for performing the reattachment of step 460. For example, as shown in
The relative placement of steps 405–460 with respect to other steps in
Other implementations are within the scope of the following claims. For example, although the examples above are given in an instant message context, other online applications or communications systems with similar attributes may be used.
This application claims priority from U.S. Provisional Application No. 60/376,181, filed Apr. 30, 2002, which is incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
5283560 | Bartlett | Feb 1994 | A |
5287514 | Gram | Feb 1994 | A |
5416895 | Anderson et al. | May 1995 | A |
5544352 | Egger | Aug 1996 | A |
5546528 | Johnston | Aug 1996 | A |
5581670 | Bier et al. | Dec 1996 | A |
5588107 | Bowden et al. | Dec 1996 | A |
5617114 | Bier et al. | Apr 1997 | A |
5617526 | Oran et al. | Apr 1997 | A |
5627960 | Clifford et al. | May 1997 | A |
5644737 | Tuniman et al. | Jul 1997 | A |
5664133 | Malamud et al. | Sep 1997 | A |
5692142 | Craycroft et al. | Nov 1997 | A |
5712995 | Cohn | Jan 1998 | A |
5721852 | Porter | Feb 1998 | A |
5742813 | Kavanagh et al. | Apr 1998 | A |
5754176 | Crawford | May 1998 | A |
5760768 | Gram | Jun 1998 | A |
5798752 | Buxton et al. | Aug 1998 | A |
5801703 | Bowden et al. | Sep 1998 | A |
5832494 | Egger et al. | Nov 1998 | A |
5838315 | Craycroft et al. | Nov 1998 | A |
5877758 | Seybold | Mar 1999 | A |
5877765 | Dickman et al. | Mar 1999 | A |
5884306 | Bliss et al. | Mar 1999 | A |
5929851 | Donnelly | Jul 1999 | A |
5937417 | Nielsen | Aug 1999 | A |
5974413 | Beauregard et al. | Oct 1999 | A |
5990905 | Chew et al. | Nov 1999 | A |
5995101 | Clark et al. | Nov 1999 | A |
6002398 | Wilson | Dec 1999 | A |
6002400 | Loring | Dec 1999 | A |
6018571 | Langlois et al. | Jan 2000 | A |
6057844 | Strauss | May 2000 | A |
6078935 | Nielsen | Jun 2000 | A |
6091409 | Dickman et al. | Jul 2000 | A |
6092068 | Dinkelacker | Jul 2000 | A |
6097389 | Morris et al. | Aug 2000 | A |
6118427 | Buxton et al. | Sep 2000 | A |
6144375 | Jain et al. | Nov 2000 | A |
6147685 | Bliss et al. | Nov 2000 | A |
6173316 | De Boor et al. | Jan 2001 | B1 |
6188403 | Sacerdoti et al. | Feb 2001 | B1 |
6229539 | Morcos et al. | May 2001 | B1 |
6233571 | Egger et al. | May 2001 | B1 |
6233726 | Bowman et al. | May 2001 | B1 |
6237135 | Timbol | May 2001 | B1 |
6246411 | Strauss | Jun 2001 | B1 |
6248946 | Dwek | Jun 2001 | B1 |
6252594 | Xia et al. | Jun 2001 | B1 |
6260148 | Aggarwal et al. | Jul 2001 | B1 |
6275790 | Yamamoto et al. | Aug 2001 | B1 |
6281879 | Graham | Aug 2001 | B1 |
6301609 | Aravamudan et al. | Oct 2001 | B1 |
6304879 | Sobeski et al. | Oct 2001 | B1 |
6317128 | Harrison et al. | Nov 2001 | B1 |
6346952 | Shtivelman | Feb 2002 | B1 |
6362842 | Tahara et al. | Mar 2002 | B1 |
6369837 | Schirmer | Apr 2002 | B1 |
6377944 | Busey et al. | Apr 2002 | B1 |
6381735 | Hunt | Apr 2002 | B1 |
6384849 | Morcos et al. | May 2002 | B1 |
6407757 | Ho | Jun 2002 | B1 |
6434599 | Porter | Aug 2002 | B1 |
6519629 | Harvey et al. | Feb 2003 | B1 |
6539421 | Appelman et al. | Mar 2003 | B1 |
6691159 | Grewal et al. | Feb 2004 | B1 |
6781608 | Crawford | Aug 2004 | B1 |
6784901 | Harvey et al. | Aug 2004 | B1 |
6907447 | Cooperman et al. | Jun 2005 | B1 |
6981223 | Becker | Dec 2005 | B1 |
20020073207 | Widger et al. | Jun 2002 | A1 |
20020097277 | Pitroda | Jul 2002 | A1 |
20020101446 | Tang | Aug 2002 | A1 |
20020130904 | Becker et al. | Sep 2002 | A1 |
20030052915 | Brown et al. | Mar 2003 | A1 |
20030142141 | Brown et al. | Jul 2003 | A1 |
20030164862 | Cadiz et al. | Sep 2003 | A1 |
20030210265 | Haimberg | Nov 2003 | A1 |
Number | Date | Country | |
---|---|---|---|
20040056893 A1 | Mar 2004 | US |
Number | Date | Country | |
---|---|---|---|
60376181 | Apr 2002 | US |