0. Used terms
1. Preface
2. Solution
2.1. Main idea
2.2. Possibility of turning on/off for all such notifications
2.3. Examples
2.3.1. Example of a window for a mouse gesture and/or a custom keyboard shortcut
2.3.2. Example of a window for a standard keyboard shortcut
2.3.3. Example of a window for a global keyboard shortcut
2.3.4. Example of a window for a possibility to turn on or turns off all such notifications
0. Used terms
0.1. “System” – Ubuntu + user environment; in this document I mean KUbuntu 12.x.
0.2. “Hotkey” – a key combination for which a user via the standard application “System settings” or via a standard dialog “Configure Shortcuts” (of any application) have previously assigned a system action and/or an action of a system component or an action of an application.
--------------------
1. Preface
The system now already has an implementation of the concept “Event” and has an implementation of some possible ways to notify a user that a such event is occurred.
1.1. Examples of such events (see in “System Settings > Application and Software Notifications”):
1.1.1. E.g.:
Event source: Accessibility (a system component)
Event title: Sticky keys has been enabled or disabled
1.1.2. E.g.:
Event source: KWin Window Manager (a system component)
Event title: Activate Window
1.2. I suppose that there are one or more specifications and/or APIs, via which an application can:
1.2.1 to provide the system with a complete list of events, any of which can be invoked by this application;
1.2.2. to notify the system that an event (one of events, specified in 1.2.1) is just occurred in this application.
The system provides a user with an ability of customization, i. e., how to notify him that a such event is occurred.
For such customization the system provides a user with a standard set of controls (see a picture:
http://content.foto.mail.ru/mail/chapaikinva/General.Public/i-64.jpg ).
The user can access this set of controls via the “System settings” (a standard application) (see a picture:
http://content.foto.mail.ru/mail/chapaikinva/General.Public/s-68.png ), as well as via the application, which is the source of the event (see a picture:
http://content.foto.mail.ru/mail/chapaikinva/General.Public/i-65.jpg ).
--------------------
2. Solution
Comment: all that is given below describes a behavior as if the solution is implemented (in fact all that is described below now is not implemented).
2.1. For any use of a hotkey as well as any recognition of an allowed mouse gesture, the system treats this use of a hotkey / gesture as a normal event, and therefore allows a user to assign to the event one or more notifications (any of which is of provided standard notification type).
The system provides a user with a standard set of controls (see a picture:
http://content.foto.mail.ru/mail/chapaikinva/General.Public/i-64.jpg ).
2.2. The system provides a user with a possibility to turn on as well as to turn off all the notifications for all such events (i. e., events of use hotkeys and mouse gestures) at once.
2.3. Examples:
2.3.1. When a user configures a notification for a mouse gesture and/or a custom keyboard shortcut, a window of “System settings” might look like this:
http://content.foto.mail.ru/mail/chapaikinva/General.Public/s-58.png .
2.3.2. When a user configures a notification for a standard keyboard shortcut, a window of “System settings” might look like this:
http://content.foto.mail.ru/mail/chapaikinva/General.Public/s-63.png .
2.3.3. When a user configures a notification for a global keyboard shortcut, a window of “System settings” might look like this:
http://content.foto.mail.ru/mail/chapaikinva/General.Public/s-60.png .
2.3.4. When a user turns on or turns off all the notifications for all such events (i. e., events of use hotkeys and mouse gestures) at once, a window of “System settings” might look like this:
http://content.foto.mail.ru/mail/chapaikinva/General.Public/s-66.png .