169253 - move oscar / IM / AIM / YIM prefs for presence out of ab .js and into mailnews.js

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Address Book & Contacts, defect)

Description

[(not reading, please use [e-mail] instead)]

move oscar / IM prefs for presence out of ab .js and into mailnews.js

this will allow power users to configure things, like ICQ, irc, MSN messenger, 
YIM, etc.

Comment 1

[(not reading, please use [e-mail] instead)]

accepting

Comment 2

[(not reading, please use [e-mail] instead)]

Or one day, add a picker menulist to prefs for: 

For instant messaging us [MSN, YIM, ICQ, irc, AIM, jabber]

and we could set these hidden prefs appropriately. 

coolness.

Comment 3

[(not reading, please use [e-mail] instead)]

not going to happen for 1.2 beta, sliding out.

Comment 4

[(not reading, please use [e-mail] instead)]

if we use the oscar url for aim presence in the hdr area, we'd use the same 
pref.

Comment 5

[(not reading, please use [e-mail] instead)]

for the oscar pref stuff (http:// urls), see:
http://lxr.mozilla.org/mozilla/source/mailnews/addrbook/resources/content/abCard
ViewOverlay.js#230

for the im pref stuff (goim: urls) see:
http://lxr.mozilla.org/mozilla/source/mailnews/addrbook/resources/content/addres
sbook.js#717
http://lxr.mozilla.org/mozilla/source/mailnews/addrbook/resources/content/abCard
ViewOverlay.js#221

Comment 6

[(not reading, please use [e-mail] instead)]

moving to 1.3 beta.

by 1.3 final, we should be IM agnostic.

Comment 7

[(not reading, please use [e-mail] instead)]

moving out, no plans to do this for 1.3, but I'd accept patches.

this would be an easy bug for someone to do.  just move code from hard coded to
prefs.

Comment 8

[(not reading, please use [e-mail] instead)]

another summary:

clean up the integration with AIM so that YIM other IM clients can integrate
with the addressbook and mail.   make it an optional tbird install, like offline.

Comment 9

[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 10

[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