> A new record type - TABLE, (actually 2 - compressed and > un-compressed) 2 new function codes, move_to (2 short > co-ord) and draw_box (2 short co-ord and a char border-width). > > To render the TABLE record, build an offscreen window (so it > can be scrolled on both axes), and place the data using the > function codes. If the cells have borders, move_to and > draw_box will construct them. Text data will be drawn at the > current location and will obey font, italic, text_color, etc. > An inline-image tag will specify an image (document) will be > drawn at the current location.
And this would give me a reasonable table on the GTK viewer on my 1600x1200 screen? 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. 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. Later, Blake. _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
