Re: [Ayatana] Two suggested designs for the Sound Indicator

[Frederik Nnaji <frederik.nnaji@xxxxxxxxx>]

On Wed, May 5, 2010 at 00:18, Jan-Christoph Borchardt <jan@xxxxxxxxxxx> wrote:

If you go out and monitor a ton of users, how many will know that a
Firefox sound control also controls Flash apps inside the browser?
They will just use the slider provided by the Flash app because that’s
what is nearby. And if the case happens where they have 20 tabs open
(rarely ever happens for normal users * **) and try to find the guilty
one, they can still use the global control.

* http://dubroy.com/blog/how-many-tabs-do-people-use-now-with-real-data/
** http://mozillalabs.com/testpilot/2009/09/30/test-pilot-ready-to-dig-into-some-data/

i would instead prefer to see a better control both for behaviour and derivable misbehaviour of the flashplugin in our browser. i don't know if it is already possible to send volume or playback instructions to the proprietary flashplugin during runtime..

how often have i used full screen in adobe's flashplugin, and once i attempted to touch the keyboard or to change brightness or volume on my netbook, fullscreen state was broken, the window focus is lost to the naked unintuitive markup page hosting the video, the user experience is betrayed.

how about detecting that a flash movie is playing and changing the system's keymap into movie mode!?
filter the keyboard input device event stream to adobe flashplugin by Fn keypresses (cases: media keyboards, netbooks, notebooks..)  or modifyer keys CTRL, ALT, SUPER (they don't work in flash anyway) to enable advanced window management in fullscreen

fullscreen is something we need to be less stingy with..
i'm trying to consider it in context with this indicator..