merge jono's appindicator with the infamous "systray"

[Luca Invernizzi]

let's fix the last problem jono had, then we'll have our appindicator plugin.

lp:~jonobacon/gtg/application-indicator-plugin ,
http://www.jonobacon.org/2010/01/14/application-indicators-rocking-the-house/

ps: the title is really just to mess with Lionel :-D

[Paul Natsuo Kishimoto (khaeru)]

See also bug #498000.

[Lionel Dricot (ploum-deactivatedaccount)]

Can somebody explains me what's the difference between that "appindicator" and the old systray besides the name ?

[Luca Invernizzi (invernizzi)]

Sure. The idea is that it tries to put some order by providing the same features of the old systray. Basically, the systray would become a big menu.
In particular, and in no particular order:
  - it is a service run by via dbus
  - it has a notion of categories of applications (gtg classifies as a STATUS app).
  - it is done to monitor non intrusively background applications: an icon can be set to passive (invisible), active or "in need of attention by the user". I think that the idea behind this is that the user can choose if he wants to see the "active" icons or just be informed when an app needs attention
- it's not gtk only (works on kde - don't ask me details on this)..

Plus, look and feel:
  - consistent UI in terms of spacing
  - a unified left click to access the menu
  - user can move between the icons with the keyboard
  - It enforces division between system and non-system icons, so that those do not mix up

It's also easier to code in many aspects (even if the documentation is non existent, and they probably are keeping the devs in a anechoic cavern).

Information is really rare and evenly distributed across the net, so I'm learning as I speak :-D