[Kst] branches/work/kst/kst1kde4/kst/src/libkst

Matthew D Truch matt at truch.net
Fri Nov 27 16:16:09 CET 2009

> The user experience question is - should we let the user delete bottom up (in 
> which case they might very well make a Big Blunder (TM) and delete something 
> important) or make them delete top down (which is safe, but possibly tedious).
> Kst 1.x did the latter, and I never minded it, since there was a 'purge' 
> convenience function in the data manager to delete anything that was unused.
> Kst2 currently does the former.

How about all of the above?  Delete lets you delete things that aren't
used.   Some kind of "force delete" which lets you remove things that
are in use (perhaps by way of an obnoxious popup warning dialog, or
perhaps you have to ctrl-delete to make them go away).  And definitely a
"purge" button which iteratively removes all unused items.  

"299792458 m/s.  It's not just a good idea, It's the law."
Matthew Truch
Department of Physics and Astronomy
University of Pennsylvania
matt at truch.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kst/attachments/20091127/cb7cacab/attachment.sig 

More information about the Kst mailing list