> > BEGIN_TABLE: 0x97 ncols:1 width:1 talign:1 border:1 bg-color:3 > > BORDER_COLOR: 0x93 border-color:3 > > BEGIN_TABLE: 0x94 ncols:1 width:1 talign:1 border:1 > > BEGIN_TR: 0x91 align:1 > > BEGIN_TD: 0x92 align:1 colspan:1 > > BEGIN_TD: 0x95 align:1 colspan:1 bg-color:3 > > END_TABLE: 0x90 > > So, what you are proposing is to have the desktop simply > substitute function codes for <TAGS> and have the Palm > actually parse and layout the table???
That's pretty much the way I read it. If you can come up with an idea that allows for all the different viewers at all the different resolutions while still not having the Palm parse and layout the table, I'm all ears. ;) Adding in the number of columns (and maybe rows too, Bill?) will allow the Palm to make a naive implementation go rather quickly (just set the drawing bounds to 1/nth the screen, and draw the row, keeping track of the length of the longest column), so we are saving some processing. I should probably let you all know that I've written an HTML Parser for the Palm for my company. I have added in table support, but have forced the table tag in the HTML to contain a palmTableSpec attribute listing the widths in a simple format. This solution would obviously not work for Plucker, unless we could generate the listing dynamically, but even then, we wouldn't know which device we were generating for, so adding in a width would probably be a bad idea. Later, Blake. _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
