User talk:Bygdog: Difference between revisions
mNo edit summary |
(Revision following feedback from bradh) |
||
Line 1: | Line 1: | ||
''Draft idea "lavalamp" event filter: 0.0.0.2'' | |||
There was an idea: ''to add '''contexts''' to KDE4''. It applied to tooltips and Konqueror-style accessibility shortcuts in the desktop (toggled by Ctrl). Using a taskbar or desktop extension, the user was could set the context of messages. Context was defined as ''declared user activity''. Messages would change depending on the user's chosen context. | |||
DCOP could be used to display the messages, after the program and its GUI retreived out what to display, and how. | |||
{{tip|[[Image:20070319-titletooltip-KDE3.jpg]]}} | |||
For example, if the user wanted to work with development they would declare it using the program GUI so that tooltips for widgets would supply relevant information. They displayed the relevant source code ("'''development activity'''" context). In other activities, the tooltips showed a position in an ordered task trail ("'''workflow'''" context) or displayed a translation ("'''linguistic activity'''" context). | |||
This proposed implementation seeks to be small, simple, effective and extensible. It could help contributors who want to participate more effectively in KDE development. The infrastructure needed may already be in the KDE code base. | |||
There may be a problem getting applications to give up their ''regular'' tooltips for alternative tooltips. | |||
Code links: | |||
http://doc.trolltech.com/4.0/signalsandslots.html | |||
http://www.phptr.com/articles/article.asp?p=667415&seqNum=3&rl=1 --from bradh on irc |
Revision as of 11:42, 20 March 2007
Draft idea "lavalamp" event filter: 0.0.0.2
There was an idea: to add contexts to KDE4. It applied to tooltips and Konqueror-style accessibility shortcuts in the desktop (toggled by Ctrl). Using a taskbar or desktop extension, the user was could set the context of messages. Context was defined as declared user activity. Messages would change depending on the user's chosen context.
DCOP could be used to display the messages, after the program and its GUI retreived out what to display, and how.
For example, if the user wanted to work with development they would declare it using the program GUI so that tooltips for widgets would supply relevant information. They displayed the relevant source code ("development activity" context). In other activities, the tooltips showed a position in an ordered task trail ("workflow" context) or displayed a translation ("linguistic activity" context).
This proposed implementation seeks to be small, simple, effective and extensible. It could help contributors who want to participate more effectively in KDE development. The infrastructure needed may already be in the KDE code base.
There may be a problem getting applications to give up their regular tooltips for alternative tooltips.
Code links: http://doc.trolltech.com/4.0/signalsandslots.html http://www.phptr.com/articles/article.asp?p=667415&seqNum=3&rl=1 --from bradh on irc