Re: [Ayatana-dev] statusicon -> AppIndicator (popup-menu signal)

[Alex Cornejo <acornejo@xxxxxxxxx>]

Thanks for your reply Ted.

> In general, we're not super interested in people implementing this type
> of behavior.  It isn't good for the user experience in that there is
> always going to be a delay in the menu appearing.  While this isn't a
> big deal on your laptop, it in, for instance, small webbooks with 800Mhz
> ARM chips.

For what its worth, I am implementing it on netbook with an atom
processor, and there is no lag here. What is unfortunate, is that
almost every app these days is coded in python, so you can have a 40mb
process running on your machine, whose only job is something as simple
as presenting an email icon when you got new mail. Of course, I
understand why people love python (I love it too), but for things that
will be running all the time on every ubuntu system out there, it
would be nice to keep it all C/C++. In the app I am porting to
appindicator the only operations that I need to do to generate the
menu is one xrandr call and some string operations in C, all of which
is probably faster than the widget rendering routines, but I am
digressing.

> That all being said.  People do it.  You can get the dbusmenu
> representation of the menu and watch the presentation signal on the menu
> to know when it is displayed.

Thank you, I'll look into it.

> Yes, you can do this using udev.  There is a GLib based library call
> gudev that will give you signals when devices are plugged in.  This is a
> much better way to update the menu and makes a better user experience.
> You can look at the indicator-session codebase as an example there, it's
> being used for the new device features.

That seems like a better alternative, I'll look for documentation on
this and see if it will work for my needs (I really just need to know
if a display device was plugged in, so if the right signals are there
I'll go through this route).

Thanks again,

Alex