---On Wed, 30 Oct 2002 12:17:34 PST, Bill Janssen said
> Actually, I'd rather do tables right, rather than using some
> (opinion-deleted) image scheme. That is, define a new record type or
> function codes in the text record for them, encode their information,
> and display it properly in the viewer. I'd be happy to help with the
> record design, and of course the distiller, to make this work. And
> I'd be happy to implement it in the GTK+ viewer. I think this would
> work better in the long run.
My suggestions were prompted by my _immediate_ need and the comments
of several people recently on the list. I agree that the -------- image
scheme is not the best solution, but, it is 100 times better than the
non-table-list-the-cells that we do now.
Anyway, how's this for a suggestion?? I can't speak to the parser end,
but, maybe David and some of the Python gurus can.
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.
--re: Re: Tables Conversion
Chris
Christopher R. Hawks Software Engineer
Syscon Plantstar a Division of Syscon International
-------------------------------------------------------------------------
Windows without the X is like making love without a partner.
win-nt from the people who invented edlin.
Linux, the way to get rid of boot viruses
-- MaDsen Wikholm, [EMAIL PROTECTED]
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
