I wrote an updated version of my previous article (in French) about the Trash, now in English. It is called I Don’t Want to Care About (the) Trash.
I wrote an updated version of my previous article (in French) about the Trash, now in English. It is called I Don’t Want to Care About (the) Trash.
Comments
13 responses to “I Don't Want to Care About Trash1 min read”
Your mockup may be good for Jack Bauer, the protagonist of the American television series 24, but not for average user…
Imagine that i open the trash-can and see that there is 5 seconds left ?! Argh! How can i stop that countdown ? Shall i cut the the red or the green wire ?
Seriously, allowing automated individual file deletion based on “time since deletion” is the only way
Yeah, it’s just that, a mockup. Not a solution, as the solution would be per-file pruning. The problem is I don’t have a mockup for it. I’ll add one to the post, but it’s most likely not the best way to present the information. I do like the Jack Bauer mention though (even if I never watched 24 🙂
the 2nd mockup looks nice
i guess that the contextual menu of each file could have an option to allow the user to say “PC, don’t delete that file until i say so” ?
it’s easier than that… if the user does not want the file be deleted … he moves it out of the trash! 😉
You’re right !
Besides, GVFS will provide a restore option.
If only developers could make it true
Comparison of Gmail UI vs Kiddo 2nd mockup :
Gmail has one warning for the whole trash-can that says “les messages se trouvant dans la corbeille depuis plus de 30 jours sont automatiquement supprimés” (that means something like : messages in trash-can that are 30 days old will be automatically deleted)
Your system consist in different warnings (one per file) saying “expires in …”
Your system is more precise and more useful (precise doesn’t always implies useful but in this case it does). I prefer by far your system.
But shall we consider adding a Gmail-like warning to your mockup ?
In other words : in your mockup, Gmail warning is implicit, shall we make it explicit ?
implicit vs explicit? I don’t get it…
are they not mutually exclusive anyway? You can’t say there is a global expiry time if files have individual expiry times, that means the global one (or individual ones) would override the other?
that’s not global
“messages in trash-can that are 30 days old will be automatically deleted” means each message that is 30 days old will be automatically deleted
actually it is implicit in your mockup that each file that is 30 days old (for instance) will be automatically deleted since a countdown is displayed. Therefore if i open the trash just after i’ve deleted a file i will see “expires in 30 days”
But it’s not explicit since if i open the trash at any other instant i will not know what is the delay before file-deletion
That’s why i wander if the mockup should also display that information : “files in trash-can that are 30 days old will be automatically deleted”
oh, makes sense. We could have something like “each files expires after [24 hours]”, and 24 hours is a clickable button to set the preferred expiry time. Win!
i was thinking about something like that
Corbeille Vider la corbeille x
Les fichiers se trouvant dans la corbeille depuis plus de 30 jours sont automatiquement supprimés
_________________________________________________________________________________________________
File 1
expires in..
Plus a gconf key to modify the delay before file-deletion
Considering the fact that some people are not geek (i know, it’s hard to believe) a default 30 days delay seems appropriate :
some people may use their computer once a week
some people may use their computer and then go in vacation during 15 or 21 days
A 30 days setting take these cases in consideration
that’s why it is a mockup and also why it’s intended to be configurable. 24 hours was purely arbitrary.
i know!
that was my 2 cents for the debate