> Perhaps we could just add a few more function codes, > TableRowBegin, TableRowEnd, TableDataBegin, TableDataEnd. > with the default TableRowBegin inserting a bold line, and > the default TableDataBegin inserting a narrow line. > > Then, the individual viewers could be updated to do > things with tables, if they thought they could handle it.
Yes, that's what I was thinking of. The additional function codes would really be hints, though, and the current <HR> codes would also be there. Newer versions of the viewer could read the hint, and instead of displaying the embedded <HR>, would instead know where the table-row and table-column boundaries are, and could display the table more intelligently. Older versions of the viewer would continue to operate as they already do. > There should also be a TableStart and TableEnd codes, so that > we can have multiple tables one after the other without them > blending into a single table. As a further optimization, we > could include the number of columns as data for the TableStart > so that a naive implementation for the Palm could split the > screen into equally-spaced columns, and draw the contents for > each row into the (tiny) space given. Good ideas. Bill _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
