On Tuesday 10 September 2002 14:55, Lubos Lunak wrote:
> On Monday 09 September 2002 20:47, Carsten Pfeiffer wrote:

> > There is no messing with the autostart folder anymore, just some
> > config->writeEntry( "AutoStart", bool );
>
>  You cannot denny that the way Klipper is started is somewhat non-standar=
d.
> And BTW, if one quits Klipper, says not to start it again and then changes
> one's mind, and has no clue about playing with config files, what is this
> poor person supposed to do ? ;)

Actually; from the user POV its the normal way. Its the best in KDE in  my=
=20
book since quitting it asks you if you want to shut it down for this sessio=
n=20
only!
Perfect! (Well; that question could be better :)
If only kalarm would do it like this...

I really do have a problem with kicker being an applet only, this is usabil=
ity=20
stuff only though.
Kicker applets that the user feels are applications (kmix, kicker) are not=
=20
found by any of the people I introduced to KDE (which says a lot :)
They simply did not look in the popup menu to add an applet to kicker! In=20
other words, nobody expected it to be an applet.
Quitting it seemed impossble as well; everyone is expecting a 'quit' menu=20
entry while they have to use the applet-bar. We actually have in internally=
=20
inconsistent way of quitting stuff on the panel :}

In this case I think we are far better off by a systray entry like the=20
standalone version has. If you can start an applet (via dcop?) from the=20
K-menu and put its icon in the systray it would be a lot clearer for our=20
users.
I would even go as far as to disallow a seperate applet taking space on kic=
ker=20
since that really does not make it clearer.
Well, maybe in a config setting somewhere hidden far out of harms way.

=2D-=20
Thomas Zander                                           zander@planescape.c=
om
                                                 We are what we pretend to =
be