One possible way would be to try to optimize the number of tables by making assumptions about the context in which a specific template is rendered (for example with controls). In the current setup, each controller, control and portlet takes no risk with its context and sets up its own HTML table to ensure display consistency.
Another way to possibly optimize the layout for NS, is simply to try and kill the outer most table (spanning the complete page) and rely on <layer> or <div> tags + Javascript to setup the overall layout. The real performance killer in NS table implementation is the un-dimensioned outer tables, as NS4 has a completely screwed algorithm to compute the table dimensions. However, none of these solutions are really simple to setup. > -----Message d'origine----- > De : NAJMAN Yves - SOP ( [EMAIL PROTECTED] ) > [mailto:YNajman@;sophia-antipolis.sema.slb.com] > Envoyé : mercredi 30 octobre 2002 11:23 > À : Jetspeed Users List (E-mail) > Objet : Jetspeed and Netscape 4.7 > > > Because Jetspeed construct pages with many HTML tables, > Netscape 4 takes a > looooong time (minutes) to display a rich page (many > portlets). As far as I > know this is a problem in Netscape that have an horrible algorythm for > imbricated tables. > > Did anyone find a quick hack that would make Jetspeed usable > under Netscape > 4.7 > > ___________________________________________ > Yves Najman > phone : +33 4 9295 2330 > fax : +33 4 9295 2262 > [EMAIL PROTECTED] > SchlumbergerSema > Le Millénium - 150, allée Pierre Ziller > B.P. 279 > 06905 Sophia Antipolis Cedex > FRANCE > > -- > To unsubscribe, e-mail: > <mailto:jetspeed-user-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: > <mailto:jetspeed-user-help@;jakarta.apache.org> > -- To unsubscribe, e-mail: <mailto:jetspeed-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:jetspeed-user-help@;jakarta.apache.org>
