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

List:       kde-usability
Subject:    Re: OT: Fwd: Re: Lost all KControl modules
From:       Irwin K <emerald-arcana () rogers ! com>
Date:       2002-06-29 5:33:06
[Download RAW message or body]

On Friday 28 June 2002 04:08 am, Chris Howells wrote:

> > Worse, this is an *UNRECOVERABLE* option.  Because you've destroyed the
>
> So is rm -rf /.

Yes... but you don't play with rm -rd /. like you do with "cut and copy" on 
KMenuEdit.


> OK, so deleting the KMenu is only a tiny fraction of what _could_ go wrong.
> Do you want to provide "backups" for the rest of things that could go
> wrong? What happens if you delete the backups and the thing restoring the
> backup?

Well, the bug here is that if I deleted the "Preferences" menu in KDE, I end 
up losing the entire KControl panel, requiring a reinstall.

This isn't quite the same, in my opinion, as typing rm -rf in a shell or 
deleting a kicker icon by mistake just because it's not a predictable error.  
My gripe about this is that I did not expect KDE to hose KControl if I delete 
the Prefences menu.  I expect KDE to be hosed if I type rm -rf in a shell or 
if I drag and drop an entire system folder into the trash can and empty it.  
I may accidentally type it, but when I do, I swear profusely and try to 
recover.

It's the case of something being predictable or not: whether an innocent 
action may have dire consequences.  It is very similar to people who try to 
click the Start button in Windows and accidentally put their taskbar on the 
side of the screen: they simply didn't expect the kind of behaviour and now 
they don't know how to fix it.  Similarly, by deleting the Preferences menu 
in the KMenu, I don't expect me to lose all of my KControl panels for my 
entire system.

-- 
-- Arcana  (Irwin)
_______________________________________________
kde-usability mailing list
kde-usability@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-usability
[prev in list] [next in list] [prev in thread] [next in thread]