Yohanes, I have a couple of suggestion, although no specifics. 1) Simplify the jetspeed template to minimize the use of tables.
Jetspeed.vm creates a table to that table that contains the portlet title bar and a table that contains the content. Nesting the tables in this way greatest flexibility. You may be able to replace tables with javascript, or some other HTML. Also by placing the icons before the title and minimizing the number of columns displayed, you may be able to remove the tables altogether. This simplification may reduce the useable functionality, i.e. nested tabbed panes may not display correctly. But, if you are not using the functionality, i.e. nested tabled pane, do you care? 2) "intercept the final output before it reaches the browser". You will need to understand how Turbine is used to assemble the page. I would start in jetspeed.modules.pages.JetspeedTemplatePage. Good luck. Questions about nested table and Netscape 4.x appear on this mailing list periodically. I, and the community, would appreciated knowing how you solve it. Paul Spencer Yohanes Santoso wrote: > Hi, > > Using Jetspeed for any non-trivial task almost always produce HTML > that caused the 'nested table' symptoms in Netscape 4. Replacing > Netscape with other browsers such as IE or Opera is not an acceptable > solution in my case. > > Is there anyway to intercept the final output before it reaches the > browser? I think I can write a code to optimise the <table> usage on > an HTML stream. It certainly looks feasible because many times, the > tables just redefine what its parent's attribute. > > Of course, putting a proxy machine between the Tomcat and the browser > that will do just that. But that's ugly. > > YS. > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
