Latest revision as of 17:19, 19 August 2007

D(r:)aft idea lavalamp event filter: 0.0.0.2

Activity- & Task-oriented Messages

The user sets their activity in a Kicker extension. The extension runs specific applications and refers to defined information resources ─ specified URIs, directories, files and metadata. Information is displayed to facilitate and guide the user through their chosen activities.

The kicker extension optionally logs the user's choices of activities. When they select a subsequent activity, the user can choose to comment on their progress. The comment gets stored in Kontact or another user-defined personal information management suite.

Tip

Generally, this idea applies to such things as 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.

Use Case Examples

Coding

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).

Work Trails

In other activities, the tooltips indicate a position in some defined task trail (workflow context).

Learning a Language

For this activity we want to displaying translations (language work context). The information to display would not be compiled in, but lifted from a specified reference file or directory.

This proposed implementation of the kicker plugin seeks to be small, simple, effective and extensible. Almost all of it can be done with scripts, too.

Applications may not want to give up their built-in tooltips for alternative information.

@@ Line 1: / Line 1: @@
-Once, there was an idea: ''to add '''contexts''' to KDE4''. Among other things, this was to apply to tooltips. Somewhere in a taskbar or desktop extension, the user was to be able to use DCOP shortcuts to set the context of messages. Context was to be defined as ''relating to the current activity of the user'' and meant that messages would be different depending on the user's choice of context.
+''D(r:)aft idea '''lavalamp''' event filter: 0.0.0.2''
-[[Image:20070318-titletooltip-KDE3.png]]
+= Activity- & Task-oriented Messages =
-For example, if the user wanted to work with development, tooltips for widgets would supply relevant information. Instead. they displayed the relevant source code ("'''development'''" context). In other user activities, the tooltip showed an ordered task trail ("'''workflow'''" context) or displayed a translation ("'''linguist'''" context).
+The user sets their activity in a Kicker extension. The extension runs specific applications and refers to defined information resources ─ specified URIs, directories, files and metadata. Information is displayed to facilitate and guide the user through their chosen activities.
-Now, requiring (Super-) Karamba for this sort of thing seems excessive, since the context feature described here is simple. The infrastructure needed is, without little doubt, already in the code. The proposed feature is good because it could lower the bar for contributors who want to participate in KDE, but who are hindered by current documentation. The issue of code contribution and documentation improvement is a chicken-and-egg problem. Documents need to improve but so does code, and it is hard (impossible?) to have one without the other.
+The kicker extension optionally logs the user's choices of activities. When they select a subsequent activity, the user can choose to comment on their progress. The comment gets stored in Kontact or another user-defined personal information management suite.
-:(
+{{tip|
+Generally, this idea applies to such things as 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.
-Internal error
- Could not copy file "/tmp/php6983Ko" to "/home/danimo/public_html/wiki/images/5/59/20070318-titletooltip-KDE3.png".
+                    [[Image:20070319-titletooltip-KDE3.jpg]]
-"""
+= Use Case Examples =
+== Coding ==
+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).
+== Work Trails ==
+In other activities, the tooltips indicate a position in some defined task trail ('''workflow''' context).
+== Learning a Language ==
+For this activity we want to displaying translations ('''language work''' context). The information to display would not be compiled in, but lifted from a specified reference file or directory.
+This proposed implementation of the kicker plugin seeks to be small, simple, effective and extensible. Almost all of it can be done with scripts, too.
+Applications may not want to give up their built-in tooltips for alternative information.
+= Links =
+== Code ==
+* http://developer.kde.org/development-versions/kde-4.0-features.html
+* 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
+== Other Interesting Sites ==
+* http://linuxbios.org/Welcome_to_LinuxBIOS
+* http://www.busybox.net/about.html
+* http://www.openbios.org/Welcome_to_OpenBIOS