User talk:Bygdog: Difference between revisions

Page contents not supported in other languages.
From KDE TechBase
mNo edit summary
mNo edit summary
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.
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.


      [[Image:20070319-titletooltip-KDE3.jpg]]
                [[Image:20070319-titletooltip-KDE3.jpg]]


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


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

Revision as of 10:31, 20 March 2007

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.

               

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

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.