Hi, I particularly like the interactive versions of complex data structures.
One specific person I would like to mention here is Ben Fry [www.benfry.com]. I like the way he has been experimenting with processing [www.processing.org]. Some example of his work: http://benfry.com/salaryper/ http://benfry.com/isometricblocks/ http://benfry.com/isometricblocks/ There are many more such examples where highly complex data structures and relationships are visualized in very interactive formats. -sajid www.ssdesigninteractive.com/blog On Fri, Feb 15, 2008 at 12:16 AM, Navid Sadikali <[EMAIL PROTECTED]> wrote: > On Wed, Feb 13, 2008 at 6:25 PM, Rob Adams <[EMAIL PROTECTED]> wrote: > > > There's nothing wrong with data grids per se. > > > Technology has tendencies which affect our behavior perniciously - the way > in which we converse and express. So I don't think a data-grid can > be right or wrong, but dangerous yes. Data grids are dangerous. > > The danger with data grids is two-fold > > a) They imply a transactional means of interaction. You enter input fields > into a search and a datagrid binds outputs. Input entry from user, grid > bound output from computer. Stimulus, response. > > b) They imply a means of information/visualization. Namely, data cells in a > regular grid. > > Want an example of where the datagrid might be dangerous, but nonetheless > *the > default strategy*? A normal train schedule search. I want to find a train > to go from place A to place B at time X. > > *Data grid Ixd: * Input: place A, place B, time X. Press Search. > Output: rows of matching train entries. Don't find what you are looking > for? Modify A, B, or X and repeat. > > *Data grid Visualization:* Data are values placed in a grid cell. > Stations, times, and everything else. > > *Problems with the Data grid approach:* User must find appropriate trains by > mental calculation from data. If user doesn't find what he wants, or is off > on the times, he begins the dialogue over again. > > *Non data grid IxD:* Inputs are places on a map. Train time starts now, so > no input required. > > *Non data grid Visualization:* A time schedule where the horizontal axis is > time and trains are placed on it. > Just look here: http://worrydream.com/bartwidget/ (thanks to Aza Raskin > for this example) > > *Solutions inspired by alternative approach:* A seamless interactive > input-output dialogue of dragging stations around which inspires more "what > if" scenarios. This solution lets people *see time and compare trains*, it > is oriented around planning your route. > > Therefore, the problem with data grids like any technology is that it > curtails our thoughts and limits our expression, and suggests that all > problems are readily solved by using it. > > > Navid Sadikali > Agfa Healthcare > Interaction Design > > > ________________________________________________________________ > 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 > ________________________________________________________________ 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
