Re: Ark: extract and quick extract

On Saturday 18 July 2009 03:26, Raphael Kubo da Costa wrote:
> 2009/7/17 Peter <gostelow@xxxxxxxxxxxx>:
> > On Friday 17 July 2009 15:01, Raphael Kubo da Costa wrote:
> >> 2009/7/17 Maciej Pilichowski <bluedzins@xxxxx>:
> >> > There should be a way for user to, "just do it", extract files. The
> >> > straightforward usage (basic one) should not pay penalty for being
> >> > able to do more complex things.
> >>
> >> I personally think a button that extracts the files without further
> >> interaction can be quite confusing. Suppose the user is in $HOME and
> >> types 'ark /tmp/foo.zip' in a console. If she presses the "quick
> >> extract" button, should it extract the files to /tmp or $HOME?
> >
> > The quick extract always uses the current working directory (cwd). Recent
> > folders override the cwd. The user should be able to set a recent folder
> > as the new cwd and continue with quick extract. A 'keep cwd in sync'
> > should automatically set cwd to the selected recent folder using a normal
> > extract, followed by repeated quick extracts.
> >
> > I see the following usage:
> >
> > 1- All extracts done in different directories: normal extract only +
> > recent folders.
> >
> > 2- Some extracts done in different directories: sync cwd with recent
> > folders, first use normal then quick.
> >
> > 3- All extracts done in one directory: set cwd, if necessary, and use
> > quick extract.
>
> I'm sorry, but I didn't fully understand what you mean. Doesn't this
> make things even more complex?

Okay, let me explain it another way.

A normal extract is used to both set the quick destination directory and 
extract. The exception is when the extract is to the cwd. The sync cwd 
checkbox allows ark to move the cwd for each normal extraction, thus allowing 
quick extract to work for all directories.

Instead of changing the cwd, ark may use a 'quick directory' and not change 
the cwd. When the user checks the sync, the quick dir is immediately set to 
the selected destination. Thereafter, quick extract will always extract to 
the last normal extract destination, when sync is checked, and fixed to the 
last destination, when sync is unchecked.

For example, I have cwd set to $HOME and want to extract from /tmp. With sync 
quick unchecked, quick extract will use $HOME as the destination. If I do a 
normal extract to /tmp and check sync, subsequent quick extracts will 
use /tmp, not $HOME.

If I now do a normal extract from $HOME/download, with destination $HOME/prj, 
quick extract will now extract to $HOME/prj, not /tmp.

If I now uncheck sync quick, it will remain set to $HOME/prj. So I can quick 
extract all source files there even after I used normal extract to 
$HOME/public_html, /usr/local/src, or /tmp.

Since setting the quick dir follows the same steps as a normal extract, it 
makes sense to use normal extract to set (and extract to) the quick dir.

It is necessary to show the current quick dir, but not the last normal dir. 
I'd prefer to have the sync checkbox on the normal dialog because I am doing 
an extract anyway and that's when I want to sync/unsync the quick dir.

Note, this principle is similar to find and find next. It is also used in kate 
where the terminal cwd can be set to an open file dir, so this behaviour, 
imo, is not uncommon.

Regards,

Peter
_______________________________________________
kde-usability mailing list
kde-usability@xxxxxxx
https://mail.kde.org/mailman/listinfo/kde-usability