1 |
Guy Harrison posted <200602141959.23677.swampdog-ml6@××××××××.com>, |
2 |
excerpted below, on Tue, 14 Feb 2006 19:59:23 +0000: |
3 |
|
4 |
> If I can trouble you with a further question, within kickerrc |
5 |
> [Kmenu] where do I go next to find its entries? |
6 |
|
7 |
The question doesn't quite parse as is, here, so I'm forced to make some |
8 |
assumptions about what you meant. If they are wrong, you will therefore |
9 |
find the following likely doesn't answer your question, altho it might be |
10 |
useful info in general. |
11 |
|
12 |
First, a bit of general information about the organization of kickerrc and |
13 |
its related "child" files. |
14 |
|
15 |
Kicker deals with three basic types of components, buttons, applets, and |
16 |
extensions. |
17 |
|
18 |
A button is just that. It appears as a button in kicker, and kicker |
19 |
contains the code that handles the action taken when the button is pushed. |
20 |
|
21 |
An applet is a dynamic application hosted by kicker. Examples are the |
22 |
clock and taskbar. Often, these are stand-alone applications that have |
23 |
mini-versions designed especially to run in kicker. Examples are the |
24 |
kdict applet, which puts a little text box in which you can enter words on |
25 |
the kicker panel, which then pops up the main kdict application with the |
26 |
results of the lookup, and ksysguard-applet, which allows graphs of |
27 |
various system status elements (CPU activity, memory usage, network |
28 |
activity, etc) to be displayed in kicker, just like the full standalone |
29 |
ksysguard does, but with a bit more limitation due to the kicker display |
30 |
format. |
31 |
|
32 |
An extension normally appears as an entirely separate panel. Kicker by |
33 |
default has one, called main, at the bottom of the screen, but you can |
34 |
move it elsewhere if desired, and place additional extension panels |
35 |
wherever you want them as well. One of the extensions is a normal panel, |
36 |
which, as with the main panel, can contain its own buttons and applets as |
37 |
desired. Other extensions are special purpose panels, including one |
38 |
similar to the konqueror side bar, so it's always available even when |
39 |
konqueror isn't running, another that's an icon based taskbar as its own |
40 |
panel, etc. |
41 |
|
42 |
The main kickerrc file contains information about the location of buttons |
43 |
and applets running in the main panel, as well as information about the |
44 |
location of the main and extension panels on the display, and what those |
45 |
extension panels are. For applets and extensions, the main kickerrc |
46 |
normally refers to an additional "child" file, that contains the |
47 |
configuration for that particular applet or extension. Thus, if you are |
48 |
running more than one clock (say you want a second one displaying the |
49 |
time where a friend or relative is located, so you don't have to figure |
50 |
out what time it is for him, manually), you'll have pointers to more than |
51 |
one clock applet rc file, each of which contains the configuration for |
52 |
that particular clock applet. Likewise, each extension has its own config |
53 |
file, which for panel extensions will contain information on their own |
54 |
applets and buttons. |
55 |
|
56 |
One particularly useful possibility of all this is to configure a second |
57 |
panel, so you can have one set to autohide, for stuff that you want |
58 |
available but don't want always taking up room on your display (perhaps |
59 |
the kmenu and maybe the clock), and the other set to always-on-top, for |
60 |
stuff you want visible at all times (perhaps the system status info of the |
61 |
ksysguard applet, and the system tray, maybe the clock too). |
62 |
|
63 |
So... if you see a setting in kickerrc that looks like a pointer to |
64 |
another config file, it probably is. Take a look and see if there's a |
65 |
config file by that name with more config settings, if that's the |
66 |
particular button/applet/extension you are investigating. |
67 |
|
68 |
FWIW, the screenshot I posted a link to a few days ago may be be |
69 |
interesting, if you wonder how I have mine set up. I don't believe it |
70 |
shows all my extension panels, and I'm running dual 21" monitors in |
71 |
1600x1200 resolution each, so obviously, my configuration won't be |
72 |
suitable at all for someone running a single 17" monitor in 1280x1024 or |
73 |
even lower, but it should still be interesting to see what such a |
74 |
power-user's screen looks like, and to what use he's putting all those |
75 |
pixels. I had to take down the full size version, as I'm way over |
76 |
bandwidth for the month (hopefully you can still reach the site, it was |
77 |
still working as I posted this), but the two smaller 1/3 size 256-color |
78 |
png and compressed jpg are still there. |
79 |
|
80 |
http://members.cox.net/pu61ic.1inux.dunc4n/ |
81 |
|
82 |
Back to your question... Unfortunately, the answer to where one finds the |
83 |
menu layout for KDE isn't as simple as it used to be, and to be honest, I |
84 |
can't give you as straight an answer here as I could a few years ago, |
85 |
because of that. KDE is complying with the freedesktop.org menu standards, |
86 |
which work one way, as well as providing backward compatibility with its |
87 |
own older layout, which would have been quite familiar to anyone used to |
88 |
the MSWormOS start menu, as it kept the menu in the same sort of tree, |
89 |
located at /usr/share/applnk, I believe it was. Those work somewhat |
90 |
differently. It's possible there's a third standard in there as well, |
91 |
maybe backward compatibility with GNOME's pre-freedesktop.org layout, and |
92 |
maybe others as well. |
93 |
|
94 |
In addition to the above, there's the system locations, and user's own |
95 |
locations, the configuration of which doesn't just add to the default |
96 |
system location, but can delete (by hiding) or move default menus or |
97 |
entries according to individual user preferences. |
98 |
|
99 |
Finally, the fact that Gentoo slots its KDEs so more than one may be |
100 |
installed at the same time, changes things. |
101 |
|
102 |
I do have a rather customized layout myself, which is how I know what I |
103 |
know about it, but to be honest, I'm not entirely up with the new |
104 |
defaults, as I configured my layout some time ago and haven't had to |
105 |
change it recently, as my old customizations just carried forward, so I |
106 |
didn't have to worry about it. |
107 |
|
108 |
Note that with such a lot invested in customization, I'd be very upset if |
109 |
I lost it. Thus, when I upgrade KDE, I take the precaution of copying my |
110 |
~/.kde* to a backup location. Then I start KDE as my regular user and see |
111 |
how it does. If I don't like any changes made, I can compare the backup |
112 |
config to the new one and see what changed, then change it back or merge |
113 |
my customizations as appropriate. However, I've very seldom actually lost |
114 |
settings. |
115 |
|
116 |
What /does/ sometimes happen is that the upgraded KDE doesn't like |
117 |
something about the old settings and won't run. Then I have to kill X and |
118 |
from a virtual console, usually running mc, I delete the broken config and |
119 |
let KDE build a new one from scratch. That has always worked. Then back |
120 |
out of X/KDE again, I'll delete the defaults, and copy over about half my |
121 |
customized config. They I restart KDE and see if it works. If it doesn't, |
122 |
I know the problem is in the half I copied over, so try again with only |
123 |
half of that. If it works, I know the problem is in the other half, so I |
124 |
copy half of it over (so have about 3/4 now) and try again. Eventually, |
125 |
I'll isolate the issue to a single config file, after which I'll dive into |
126 |
the file, likewise trying part of it at a time, until I find the section |
127 |
that doesn't work. Then I'll dive into that section, until I find the |
128 |
line that's causing the problem. By then, it's usually pretty obvious |
129 |
what that section and line is configuring, and I can usually just take the |
130 |
default and reconfigure it from the GUI to get the settings I want back |
131 |
again. |
132 |
|
133 |
What I'd suggest, and have used myself in other troubleshooting |
134 |
situations, is a similar strategy. Most of KDE's system settings are in |
135 |
/usr/share, and nothing in that dir should be critical to system operation |
136 |
itself, as the place for vital system config info is /etc. Thus, it's |
137 |
possible to find where a particular problem is by process of elimination, |
138 |
making a backup of the dir, then deleting parts of it from the working |
139 |
config, until you've found the effective part. This is of course made |
140 |
rather easier by common sense. The docs dir for instance shouldn't have |
141 |
any effect on configs, so you can leave it in place and not test it. |
142 |
|
143 |
Similarly with your user configs. KDE has a global ~/.kdeglobals, but |
144 |
other than that, nearly all of its config is under ~/.kde*. It's |
145 |
therefore relatively easy to (from a virtual console) rename ~/.kde* to |
146 |
*.bak, and test with a "clean" user config. If that works as it usually |
147 |
does, the simple if somewhat time consuming process of elimination |
148 |
described above can be used to trace the problem location, pinpointing it |
149 |
to any level of specificity, down to the individual line if necessary, |
150 |
desired. |
151 |
|
152 |
-- |
153 |
Duncan - List replies preferred. No HTML msgs. |
154 |
"Every nonfree program has a lord, a master -- |
155 |
and if you use the program, he is your master." Richard Stallman in |
156 |
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
157 |
|
158 |
|
159 |
-- |
160 |
gentoo-amd64@g.o mailing list |