Notification area links (Was: XML libs, Was: gconf backend)

On Sun, Sep 28, 2003 at 02:18:02AM -0400, Havoc Pennington wrote:
> On Sat, 2003-09-27 at 18:42, Daniel Veillard wrote:
> > > > <note> I would love to see the system tray implementation debugged and
> > > > integrated as maintained APIs in the toolkits for example ;-) </note>
> > > 
> > > As would I, unfortunately the spec and implementation are both totally
> > > screwed up. ;-)
> > 
> >   Can I quote you on the bug reports I get <grin/>
> If you must ;-) Link to the d-d-l threads on the UI for it, that will
> keep people busy. ;-)

Handy HIG bug here for the UI:

Crosspost threads containing Mark's proposal for notification area guidelines:

Why the notification area takes a window, not an icon:

Blinking - consistency and accessibility:

My proposal for notification area preferences:

API RFE bug:

API discussion is scattered through April 2003. Fragments begin at:

Some significant reports at

    This would seem to reveal flaws in the specs at
    Reparenting clients should not map reparented windows until
    ReparentNotify has been received with valid data - e.g., the new
    parent is what's expected. I did not see any warnings about this
    at, nor did I see any checks in the GNOME code.
    Also, I didn't see the specs prohibiting to-be-reparented windows
    from mapping themselves.

    Furthermore, it seems someone is not checking screens. Embedder
    and embedee must be on the same screen of the display.

    The EggTrayIcon widget is not designed to allow someone unfamiliar
    with the spec to make a properly functioning object. (Maybe that's
    a good thing if it discourages bad ones.) There are a few events
    that a (functionally) good tray icon will watch for and act on.
    These include plug destruction, mapping, unmapping, and resizing.
    A GObject encapsulation with signals for all important events
    is a sound approach; see the old dock API in the 1.x gnoem-panel.

    This is probably related to the previous bug.

Things mentioned in various places by various people (myself included)
for which I'm not going to look up the links at this time:

  Transient device icons for mounted drive, hotplug devices, and the like
  should be placed in the notification area because:
   - Except for items such as the trash, the desktop should the user's space.
   - The desktop may be obscured by many windows, but the panel (on which
     is the notification area) stays above all but a few windows. Thus
     transient device icons in the notification area provide ready access
     to objects needed for what is often the user's task at hand.
   - WindowsXP does it; make your marketroid happy.

  Some applets such as the weather, mail, and wireless connectivity applets
  should be notification area items. Some items presently appearing in the
  notification area should be applets instead.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]