I would second the recommendation to look at Tufte. The basic issue here is that grids are easy to implement, but rarely good for users. There are numerous tactics that you can use to avoid (or minimize) the use of grids in your applications.
I would start by questioning your first assumption: WHY are you displaying large amounts of data? Is it because the user needs to see a large amount of data, or is because you are using one general-purpose display mechanism to serve many needs? If the user really needs to see a large amount of data, then I would move to a graphic visualization. That is usually a better way to create meaning than a massive grid. If the answer is the latter, then you should start teasing out the use cases, needs, and goals, and the begin creating more targetted presentations to support them. These targeted presentations will likely require less data, and can then be created without using a huge grid. I've used both of these tactics successfully for financial services apps. Good luck... Thanks, JS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=34312 ________________________________________________________________ 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
