KDE TechBase
  • User page
  • Discussion
  • Edit
  • +
  • History
KDE TechBase is a Wiki - You can help! Please contribute! Questions?

User talk:Bygdog

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

Contents

  • 1 Activity- & Task-oriented Messages
  • 2 Use Case Examples
    • 2.1 Coding
    • 2.2 Work Trails
    • 2.3 Learning a Language
  • 3 Links
    • 3.1 Code
    • 3.2 Other Interesting Sites

[edit] 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
noframe
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.

                   Image:20070319-titletooltip-KDE3.jpg

[edit] Use Case Examples

[edit] 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).

[edit] Work Trails

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

[edit] 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.

[edit] Links

[edit] 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

[edit] Other Interesting Sites

  • http://linuxbios.org/Welcome_to_LinuxBIOS
  • http://www.busybox.net/about.html
  • http://www.openbios.org/Welcome_to_OpenBIOS
Retrieved from "http://techbase.kde.org/User_talk:Bygdog"

Navigation

  • Home
  • Help
  • Recent changes

Sections

  • Getting started
  • Development
  • Schedules
  • Policies
  • Contribute
  • Projects

Toolbox

  • What links here
  • Related changes
  • User contributions
  • Upload file
  • Special pages
  • Printable version
  • Permanent link

Personal tools

  • Log in / create account
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V. Qt® and Trolltech® are registered trademarks of Trolltech ASA. Linux® is a registered Trademark of Linus Torvalds. | Legal