- From: Andrew Fedoniouk <news@terrainformatica.com>
- Date: Sat, 15 May 2004 09:44:59 -0700
- To: "David Woolley" <david@djwhome.demon.co.uk>, <www-style@w3.org>
Hi, David, "the centre column should be sent first," this is just your good wish. Could you provide a practical solution of how to implement this "incrementally"? Without such a solution I am reading yours "That's not true" as "That's probably not true" And define, please, the main goal of "incremental rendering". What is this for? To show to user something as soon as possible to keep him/her busy? Or to let him/her to decide does he/she need this page at all? Or what? Here is my own classification of sites and types of pages in the internet: 1) "portal" - navigation elemenets, not so much information - finite x/y layout primarily. 2) "documentation" - just information - infinite x/y layout primarily. 3) "applications" - navigation elemenets and input elements - finite x/y layout is a must - demand of ergonomics. Only second group needs to be rendered incrementally. In other two groups this requirement just does not make any sence. Final layout of such sites is an information itself - aesthetical information if you wish. In my personal opinion, Andrew Fedoniouk. From: "David Woolley": > > > Any layout which use columns (implemented in any way but not frames) is by > > HTML nature cannot be rendered incrementally. > > That's not true. For the typical three column layout, and assuming a > detail page, the centre column should be sent first, and rendered incrementally, > so that users can start reading it, either completely, or enough to > determine whether they are in the right place, and the other columns > should follow. > > (Personally, I feel that better support for link elements would have > removed the need to embed the index level pages in the detail level > pages.) >
Received on Saturday, 15 May 2004 12:45:30 UTC