Re: Ark: extract and quick extract

2009/7/17 Maciej Pilichowski <bluedzins@xxxxx>:
> On Friday 17 July 2009 17:01:16 Raphael Kubo da Costa wrote:
>> > 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.
>
> Why? Forced interaction (just to give some interaction) lowers
> productivity. No giving feedback (information) is another story, user
> should be informed that unpacking was successful/unsuccesful.
In this case, I don't think it's forced interaction. We may be
thinking in different terms here: if quick extraction was something
clear and didn't cause the user to have doubts, there'd be no point in
forcing him to choose a directory (and it wouldn't be quick anymore ;)

>> Suppose the user is in $HOME
>> and types 'ark /tmp/foo.zip' in a console.
>
> Is this the same as typing "ark" and then using GUI
> opening "/tmp/foo.zip"? I guess, yes.
It depends. You will end up opening /tmp/foo.zip, but your current
working dir would still be $HOME, not /tmp as would be the case if you
were using, for example, Dolphin.

>> If she presses the
>> "quick extract" button, should it extract the files to /tmp or
>> $HOME?
>
> If my guess (above) is correct then in archive (/tmp). "Here"
> means "next to the archive file".
As I said above, the problem lies in the current working dir, which
may not be the same as the target file if you're not using a file
browser. "Here", in this case, could mean either $HOME or /tmp.
_______________________________________________
kde-usability mailing list
kde-usability@xxxxxxx
https://mail.kde.org/mailman/listinfo/kde-usability