"again, the case of floating systray would not be covered, would be easier (and would not put visualization hints in the protocol) to adjust the click coordinates to something prettier, like in the case of a bottom dock, the coordinates would always be the top left corner of the icon for instance, so the menu would also always appear in the same position (not depending where was clicked in the icon)" >>> the size of the icon doesn't matter a lot, since the menu is completely at the wrong place (not just few pixels). Please take a look at this video I made : <a href="http://www.youtube.com/watch?v=M_AHFM0PNtk">http://www.youtube.com/watch?v=M_AHFM0PNtk</a> we can see that the menu is placed relatively to its top-left corner, when it should be its bottom-left corner. The application can't know this fact, only the applet can know, that's why I think it should be passed to the method. Adrien Gateau told me about using dbus-menu as a workaround, I'll make another post to reply to this point. "the ones in the spec right now are fine i think, plus some other, like some ideas about other that would be needed?" >>> could just be done with a \n in the string. I think to keep all the representation equivalent between all docks/panels, we shouldn't try to add too many markers. Anyway, an exhaustive list would be welcome. "ok, will make clear, in fact our mixer decreases the volume with mouse wheel going down, as one would expect" >>> yes, because the panel sends -1 to scroll down, and the applet then add -1 to the sound. If tomorrow another panel sends +1 for scroll down, the user will have a bad surprise. There is a tacit agreement on the meaning of the value sent on scroll, so this should just be written in the spec I think. Anyway thanks for your work on getting rid of the X systray ^^