204664 - [gtk2] biff notification using new panel spec widget

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Christopher Blizzard (:blizzard)]

It would be nice if we had a little biff icon for mail/news like windows does. 
With the new panel spec and an easy-to-use widget, this should be pretty easy to
do now without pulling in all of GNOME.

Comment 1

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

you want biff integration,w ith the OS, right?

see this: nsMessengerWinIntegration.cpp

we need one for Linux

the interface is nsIMessengerOSIntegration

we try to do getService on the contract id
at the right time, see nsMsgAccountManager.cpp

but we expect the service to do all the work it wants.
we don't call it directly.

so, register as a folder listener (for new mail notification)

so you should do it that way.

Comment 2

[David Perry]

Something like this would be particularly handy for Thunderbird, too -- perhaps
moreso than the application suite, which at least notifies you in other app
suite windows with that little green arrow.

I'm not sure it's GTK2-specific, though.  I get the impression there's a
standard for "tray icons", and I know it's supported in KDE, Window Maker and
OpenBox, among others (through plugins, for the last two).

FWIW, GAIM (http://gaim.sf.net) has a tray-icon plugin, maybe some of the code
there could be useful.  Also, the aforementioned WM/OB tray plugin is at
http://icculus.org/openbox/2/docker/ if you want a look at the other end.

Comment 3

[Christopher Aillon (sabbatical, not receiving bugmail)]

I extremely dislike nsIMessengerIntegration requiring mailnews to have such OS
specific knowledge, and essentially codeforks of the biff stuff.  There should
be an nsISystray in widget/ or something to which mailnews could call into. 
Then we could consolidate all the OSIntegration files into one, and make the
code much more extensible.  To implement this for a platform, you'd just
implement nsISystray rather than have to re-write the actual integration code
each time.

Anyway, this is a dupe of bug 18732 I believe.

Comment 4

[Ilya Konstantinov]

Blizzard, could you give some URLs about this new "panel spec" and "easy-to-use 
widget"? 
 
Re gaim: they ripped out their systray widget from libegg. So did I, in my Free 
Desktop Integration extension (see bug 18732). libegg's license isn't very 
friendly with Mozilla, and anyway, we rather need nsISystemTray with per-OS 
implementations and then implement systray biff for all OSs in a single place. 
 
Indeed this discussion could be a followup to bug 18732. 

Comment 5

[Christopher Aillon (sabbatical, not receiving bugmail)]

http://www.freedesktop.org/Standards/systemtray-spec

Comment 6

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

[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