TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Of course I know about dynamic data. The question is about screen real estate when you need to present a matrix -- dynamically generated or not. Saying you give the user a way to manipulate data or ask questions kind of kicks the can down the road. How do you present the manipulations?Â
For a flight app, taking dates and destination might be ok. But not all software is as simple as that. Even then, there are still times when you want to see the full schedule... You still have to present a table in that case... Or something similar that works in the limited real estate.
From: "mbaker -at- analecta -dot- com" <mbaker -at- analecta -dot- com>
To: 'Chris Despopoulos' <despopoulos_chriss -at- yahoo -dot- com>; techwr-l -at- lists -dot- techwr-l -dot- com
Sent: Thursday, June 23, 2016 7:53 AM
Subject: RE: HTML5, Phones, and Tables
We should think of tables as a way to structured information lookup for static media. In other words, they are a technique for presenting data on paper because of paper's lack of any kind of interactive features.
Consider, for instance, the time tables for a transportation company. No modern airline or bus company would dream of presenting its schedules as a static table anymore. Instead, the present a booking widget that lets you enter your starting point, destination, and travel times and automatically constructs an itinerary for you.
So the question should not be, how do we present tables in online media. We should never be thinking in those terms. We should be thinking how to allow readers to manipulate this data, or to ask the question of the system whose answer depends on this data. If we also have to present the data in a static media, then and only then should we be thinking about how to make it into a table.
The key here is to stop thinking in terms of tables and presentation and to start thinking in terms of data and queries on that data. Fall back to tables only as a last resort.
Mark
-----Original Message-----
From: techwr-l-bounces+mbaker=analecta -dot- com -at- lists -dot- techwr-l -dot- com [mailto:techwr-l-bounces+mbaker=analecta -dot- com -at- lists -dot- techwr-l -dot- com] On Behalf Of Chris Despopoulos
Sent: Thursday, June 23, 2016 4:10 AM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: HTML5, Phones, and Tables
In the old world tables are very useful. There's no better way in print to show a matrix of options, or present a comparison in one glance. For desktop online docs that translates really well... You can even use javascript to turn the table into something a bit more dynamic -- say, enable sorting of rows, for example. But tables require a lot of real estate.Â
What do you do for phones?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com
Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com
Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com
