On 20/02/11 18:39, Mitja Pagon wrote:
No, of course you are not the only person, there's lots of dissent, which is fine and stimulates discussion to get a better result.
It would not make sense to have volume controls both inside the UI, and in the title bar as an indicator. But the suggestion of course was to let apps *move* that functionality to the indicator, not duplicate the functionality. Indicators are abstract, logical entities that are exported from the app. They can thus be useful in more general cases. For example, in the window spread views, indicators could be rendered at full size, so their semantic meaning can be scanned in the spread view. They could even be interactive in those views, allowing one to set the appropriate volume for multiple windows, quickly, in the volume example.
Giving technical problems to solve is called "challenging the engineers" and we rather like to do that, and they rather like it too, round here ;-) As long as the work feels like it is foundational and will stick around for a long time and be used, solving hard problems is worthwhile.
Notify-OSD is purely for momentary events, not status. Indicators combine status and manipulation of the status, they are entirely different from notifications. Mark |
Attachment:
signature.asc
Description: OpenPGP digital signature