The column header sort solution is a "developer's solution", a techie "idea". Actually, users' needs are not "sorting by *any* column but sorting in a meaningful way, as I interpret Oliver's original question.
For example if it were a printed report, as in the sixties, is would be already sorted in a meaningful order, one that's useful for the user. A functional analyst and a domain expert would have discussed and agreed on one sort order. A software developer, instead, would say "hey, let's enable the user to sort on *any* column (so we don't have to care about finding their needs)". This "solution" delegates the analyst's duties on the users, is the "empower the user" attitude that leads to multiple individual HomerMobiles. Oliver's problem solution might well be to display the data already sorted in a useful way. This might be enough for a number of users, one that avoids "making them think". After, a "sort" button displaying a menu with predefined domain-useful options, like "by State and date" and so on. Just a few, the useful combinations. Notice that this is not a strict UI issue but a software design issue, one that requires system analysis. Well, actually, for the scenario I built in my mind ... -- Juan Lanus Software Developer ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
