Bug 175543 - save dialog: allow overwrite checkbox and keep source file name /allow change radio buttons
Summary: save dialog: allow overwrite checkbox and keep source file name /allow chang...
Status: REPORTED
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-19 03:09 UTC by Aaron Peterson
Modified: 2012-01-07 08:07 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Virtual Floppy drive is a product with one such feature. (31.13 KB, image/png)
2008-11-19 03:13 UTC, Aaron Peterson
Details
Example of how it might look -- kword (48.96 KB, image/gif)
2008-11-19 04:18 UTC, Aaron Peterson
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Aaron Peterson 2008-11-19 03:09:50 UTC
Version:            (using KDE 4.1.3)

See attachments that will be coming.

Basically, If I am downloading something, I expect the computer to remember the name it came from.  (I personally always want to choose where to put my downloads) and I don't want it to change.  

Occasionally, I want to bump up a revision number and save the file with a new name.  I don't ever want to be confused if this is going to happen or not.

I also really really hate dialogue boxes.

Basically I propose that we add:
[ ] allow overwrite (checkbox, still will give confirm dialog by default but configurabe)
( ) keep source name (*) allow name modification

Also, facilities to  disable the ok button until said conditions are imposed would be required.

I believe these won't be needed most of the time, but their presence will reaffirm users that they are not going to screw everything up


See also: Bug 170979
Comment 1 Aaron Peterson 2008-11-19 03:13:16 UTC
Created attachment 28682 [details]
Virtual Floppy drive is a product with one such feature.
Comment 2 Aaron J. Seigo 2008-11-19 03:27:23 UTC
imho the dialog just doesn't have room for such UI, and the results would be difficult to deal with for many users anyways. we have confirmation dialogs for a reason; i understand the hatred of dialogs, and hopefully one day we can do them in-window .. 

but i'd vote that this is a WONTFIX.
Comment 3 Aaron Peterson 2008-11-19 04:18:12 UTC
Created attachment 28683 [details]
Example of how it might look -- kword
Comment 4 Aaron Peterson 2008-11-19 04:46:59 UTC
Another implementation point,  
 we still need the field to type the new filename, 
it is often how we type paths to get to where we want to save stuff.

basically, a potential way to keep this functionality would be to have the filename location be filled with the source filename if the user clicks that radio button.  The only problem is the user won't know what the source filename is until it he checks it..   So we would want the filename to show next to that radio button, maybe a hidden sort of scroll window ex:  filenam...  where selecting it scrolls it to show ex: ...ilename31b.txt

Basically, the field will have to go to a not in use color scheme, but it would have to stay active to let us type in a directory.   Typing in a directory is required behavior.  Basically, if the filename were to show up on the right (not combined with the above filena... idea) and still allow users to type in a path, that would be great.  Flashing the text should be good enough, but if the user persists   The dialog would unfortunately  be something like:  "Would you like to create the directory __ If No, save file as ___, or cancel"

Simpler and probably better -- "keep source filename is checked. Please unrestrict naming or choose an existing directory [ok]"

If the path that is only typed in exists, It might make sense to have a dialog "Would you like to save "_____" to the directory "______" [Yes/No] 
(I hate dialogs, but can't always avoid them)

Really, with default settings, there would be no change other than the unavailability of the save button.  Heck, Set I can see setting the default to allow overwrite and having it be configurable.

Also if the user types something in that is not the original filename and says save, it may make sense to make the text for that option flash. (and if done again do a dialog box)


Allow overwrite -- please please consider
radio buttons for keep source name -- understood if delayed but I'm looking into it.

Comment 5 Aaron Peterson 2012-01-07 08:07:49 UTC
I still have problems with save-as dialog boxes populating the filename field with the filename I click on... loosing the server-given filename in the process, and potentially overwriting my data.