223499 - [META] better integration with users existing IM client

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Scott MacGregor]

[META] better integration with users existing IM client

Note, this doesn't mean shipping an IM client with thunderbird or the app suite.

there are already some hooks (a couple in addressbook, for example) to launch
AIM and for AIM presence.   these don't require the AIM client to run in the
same process space as mozilla.  (The presence is done using a <img
src="http://..."> trick).  Lauching an AIM message or AIM chat is done using
"aim:goim?..." urls, which does the right thing with the external AIM client.

There's a bug about doing AIM presence in the mail header pane as well.
(Netscape 7.1 does this, but it uses AIM code that runs in process.)

The addressbook does the (The presence is done using a <img src="http://...">
trick), and we can do the same thing we did in addressbook.

mozilla mail also has some built in hooks for budding icon support, but there
were heavily tied to how Netscape 7.x did buddy icons in NIM.

in addition to better AIM integration (see OE and how it integrates with AIM),
there are two other areas we should improve on.

1) support for other IM clients, like Yahoo! messenger, MSN messenger, ICQ, etc.
2) better support on other platforms.  at one point, the aim: url launching the
aim client didn't work on mac or linux.  that might be fixed now.

cc'ing rginda, as he might have comments or suggestions for how to do this in a
way where chat can use the same hooks.

Comment 1

[Sergey Kirienko]

Maybe that would be useful. There's a project, probably freezed, at MOZDEV -
http://jabberzilla.mozdev.org - about implementing Jabber IM into Thunderbird. I
think supporting Jabber as free and open-standard IM should be #1 task instead
of propietary MSN, ICQ or AIM.

Comment 2

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 3

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420