Le 23/07/2011 15:28, Lukas a écrit :
> Looks interesting :)

Thanks :)

> * But how about ability to undo changes if something wrong had gone
> (like a transaction or simulating file copying)? Like moving a source
> code without at least one file is close to no better than not moving at all.

I am not sure what you mean here, but I don't think the error dialog is
the place to add an undo feature, since you may also want to undo if the
file transfer succeeds. I think it is up to the application initiating
the file transfer to provide an undo feature, like Dolphin does.

> * The file list on the left. How does it going to perform in case if
> like 1000 files fails? is there some way to group files or have a filter
> input?

I don't think we should have too complex item selection features here:
if there are thousand errors, I assume in most cases the fix will be to
apply the same change to thousands files, so selecting them all is what
one need. If the error list is only appended to, I think the model
holding them can be implemented in a way that the list view will scale
(QAbstractItemModel & QListView support very large lists as long you
don't try to sort them). But maybe there is a need to set an upper
limit: if the number of errors is more than N, only display one line
saying "X files are unreadable".

> * [Edit file N properties] [retry]. Could it be done as a single smart
> button [Fix and retry], that would work on multiple files/dirs too?

That would be handy, but in this case there should be a way for the user
to know what the smart button is going to do. You need some confidence
into what will happen before letting your computer apply a batch change
to thousands of your precious files!

Aurélien
_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability