Re: Ark: extract and quick extract

2009/7/18 Maciej Pilichowski <bluedzins@xxxxx>:
> On Saturday 18 July 2009 05:33:23 Raphael Kubo da Costa wrote:
>
>> In this case, I don't think it's forced interaction.
>
> When user would like to pick up a directory, she/he can do this. But
> when the user would like to just unpack archive -- "you know, it does
> not matter, it is tmp anyway" -- she/he... has to pick a directory?
>
>> >> 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.
>
> Ok, true, so it is rather matter of label or defining what "here"
> means. Since in GUI mode user sees archives locations it would be
> better to unpack files next to archive.
> It could be labeled "quick extract" instead of "extract here".

How about the following:

* Two different actions, "Quick extract" and "Extract", the latter
showing the usual extraction dialog.

* "Quick extract", on the other hand, tries to extract to the
archive's directory. It only shows a popup message if something went
wrong, and the extraction progress can be seen in a notification (this
is how it currently works).

However, with "quick extract" the user won't be able to choose whether
she wants to preserve paths or open the destination folder after the
extraction. These can be done only via the extraction dialog. What
should be done in this case?
_______________________________________________
kde-usability mailing list
kde-usability@xxxxxxx
https://mail.kde.org/mailman/listinfo/kde-usability