User talk:Bygdog: Difference between revisions

From KDE TechBase
No edit summary
(http://linuxbios.org/Welcome_to_LinuxBIOS)
Line 17: Line 17:
* http://www.phptr.com/articles/article.asp?p=667415&seqNum=3&rl=1 --from bradh on irc
* http://www.phptr.com/articles/article.asp?p=667415&seqNum=3&rl=1 --from bradh on irc
* http://doc.trolltech.com/4.0/signalsandslots.html
* http://doc.trolltech.com/4.0/signalsandslots.html
Other interesting information:
* http://linuxbios.org/Welcome_to_LinuxBIOS

Revision as of 16:46, 20 March 2007

Draft idea lavalamp event filter: 0.0.0.2

How can activity-oriented messages be used in KDE4? This applies to tooltips and Konqueror-style accessibility shortcuts in the desktop (toggled by Ctrl). Using a taskbar or desktop extension, the user will set the context of messages. Context, defined as declared user activity results in different messages depending on the user's chosen context.

DCOP can be used to display the messages, after the program (applet) and its GUI retreived the display method content.

Tip


For example, if a user wanted to work with development they would declare it using the program GUI so that tooltips for widgets would supply relevant information. For example, showing the relevant source code (development activity context). In other activities, the tooltips showing a position in a defined task trail (workflow context) or displaying a translation (language work context). The information to display would not be compiled in, but lifted from a specified reference file or directory.

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 is presumably already in the KDE code base.

There may be a problem getting applications to give up their regular tooltips for alternative tooltips.

Code links:

Other interesting information: