Hi! On Saturday, 2013-08-10, Andrej N. Gritsenko wrote: > Hello!
> Kevin Krammer has written on Saturday, 10 August, at 20:04: [...] > >Right, but in the context of LXDE/Razor this is of no consequence, because > >those are the hosts. > > > >The applications offer functionality and visualization data and the hosts > >decide how to present that data and trigger functionality so that it fits > >into the host's overall design concepts. > > > >So even if the application does not explicitly set any tooltip information > >a host implementation could still show other things like icon, > >application name and status in a tooltip. > > > >Or maybe I am misunderstanding your concern. Are the LXDE or Razor > >systrays currently not showing any tooltips? > > I believe their panels show them just fine. I've just added my $.02 > about AppIndicator applets - they are uneasy to use because they require > a lot of extra clicks, as Stephan Sokolow noticed. But that it part of what the host does. The LXDE panel could simply display the tooltip on mouse hover. The KDE panel does that. > And I'm not sure if it > possible to extract status from AppIndicator applet until you click on > it, so only thing which our tray may show in tooltip is application name > which is not very useful unfortunately. Of course an application might not have tooltips. But if you compare the two situations, XEmbed vs. StatusNotifier, then in the first case you as the host can do nothing, while in the second case you can at least create a tooltip using the icon and the title. Not as useful as an application setting an explicit tooltip but already allowing users to better identify which application an icon belongs to. > It's why I'm rather avoiding any > AppIndicator applets. And I still believe desktop and tablet environments > should be different in usability. Gnome/Unity/Win8 don't agree with me, > you know. I agree as well, so do the Plasma workspace people. Which is the reason the came up with the spec, because it allows different workspaces to display and interact with the application status data in a way that fits their environment (e.g. mouse vs. touch). E.g. a desktop shell could display the tooltip on hover, activate on left click and menu on right click, while a tablet shell could display tooltip on touch, activate the window on long press and activate the menu on a swipe gesture. Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________ Lxde-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxde-list
