[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 86195] wish: kscreensaver should "play nicely" with
From:       Chris Howells <howells () kde ! org>
Date:       2004-07-29 13:28:28
Message-ID: 20040729132828.24161.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
      
http://bugs.kde.org/show_bug.cgi?id=86195      




------- Additional Comments From howells kde org  2004-07-29 15:28 -------
On 28 Jul 2004, at 19:50, Richard Neill wrote:
> Given that there are 2 screensaver systems (the KDE version and the 
> xscreensaver version), I propose a refinement to the kscreensaver 
> control panel to give the user more choice and simplicity.
>
> if (xscreensaver is installed){
>    [1] kscreensaver should have the option "use Xscreensaver, rather 
> than kscreensaver"

How does an option "use Xscreensaver rather than kscreensaver" provide 
simplicity? It assumes that the user _knows_ what xscreensaver is, what 
the differences are, and why they should even care about which 
screensaver engine they use.

> This would be especially helpful because:
>    1)Linux is about choice (and I've chosen xscreensaver because I 
> personally prefer it),
> however this process is   ugly, requiring changes to config files.

What process is ugly? What changes to config files?

>    2)When I have set up xscreensaver for other people, they find the 
> kde control centre's screensaver configuration confusing (because it 
> is configuring the wrong thing!)

That's not surprising. The control centre is meant to provide a 
completely transparent way of either using xscreensaver screensavers or 
native kscreensaver screensavers. Why do you feel the need to use 
xscreensaver manually?

>    3)The use of kscreensaver rather than xscreensaver for locking the 
> desktop doesn't have an easy workaround.

I don't understand this statement.

>    4)Xscreensaver-demo is more flexible

I'm not too familiar with it. Can you explain how it's more flexible?

>    5)xscreensaver has better behaviour with xinerama.

This is a problem in kscreensaver I admit, but I don't think ripping 
out years and years worth of testing and pretty well working code will 
help much to make xinerama work better.
[prev in list] [next in list] [prev in thread] [next in thread]