Linked by Thom Holwerda on Mon 28th Apr 2008 21:38 UTC, submitted by kiddo
Graphics, User Interfaces The trash can metaphor in computing is as old as the desktop metaphor itself. It was first introduced with the Apple Lisa user interface, and found its way to the Macintosh. Apple patented the whole idea, and sued anyone who tried to use the same name, resulting in other user interfaces implementing the exact same principle but just named differently. Despite its old age, and the fact it barely changed over the decades, many people have issues with the traditional concept.
Thread beginning with comment 312055
To view parent comment, click here.
To read all comments associated with this story, please click here.
looncraz
Member since:
2005-07-24

Personally, I'd set a global Trash can size limiter ( ala Windows ), THEN, I would only fill the trash can icon gradually as it begins to become more and more full.

The problem is not the concept or implementation, it is the presentation of the icon.

I, too, find myself deleting a file, then hiding every window then emptying the Trash - or otherwise bypassing then Trash completely if I'm certain I won't need the file any longer.

The only thing that causes me to empty the Trash so often is the appearance that it is "over-flowing." I can handle it when there are only one or two pieces of Trash, but when it gets closer to the top.. well.. OUT YA GO!

Another item of frustration is organization of the Trash's contents when possibly trying to find something which is within.

In this case, sorting by name or date is useless, by type has some value, by date deleted even more, but if you REALLY want do the Trash right.. well... I'd hate to give away the solution which will be employed in my "Loon-Tracker" ( for Haiku R1 / BeOS R5-Dano ).

--The loon

Reply Parent Score: 1