---On Fri, 1 Nov 2002 14:58:07 -0500, Blake Winton said
> 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. ;)
I won't apologize for being a bad explainer, but, I all ready did.
Given the information in the table doc, the palm draws the needed boxes
(if the table has borders) and places the text (suitably colored, bolded,
etc) in the locations specified in the doc. This is drawn on a offscreen
window (at least on a real palm) and scrolled the same way we do a large
image. I don't know how you would want to handle it on a device with a
larger screen, but, I'd suspect the same way large images are handled.
> 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.
I'd be interested is seeing that. and how fast it renders on a real
palm.
--re: RE: Tables Conversion
Chris
Christopher R. Hawks Software Engineer
Syscon Plantstar a Division of Syscon International
-------------------------------------------------------------------------
On two occasions I have been asked [by members of Parliament], 'Pray, Mr.
Babbage, if you put into the machine wrong figures, will the right answers
come out?' I am not able rightly to apprehend the kind of confusion of
ideas that could provoke such a question.
-- Charles Babbage
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
