In message <[EMAIL PROTECTED]>,
Klaus Weide writes:
> They already are separate; parsing: SGML.c; rendering: all the rest...
>
> IOW, your terminology is confusing.
Well, ok. I was using "parsing" as "parsing the HTML into elements",
not "parse the HTML into SGML bits and bobs". In that sense, the
parsing and rendering are not seperate because HTML.c performs some
rendering, and is called by the parser (start_element, end_element).
IMO, they're not seperate since you have to render whilst parsing.
You don't get a chance to do anything with the parse-tree.
> > So parse->internal objects->renderer->HText->curses|slang->screen?
>
> What's left of your "parse"?
The same as before. Lynx doesn't create internal objects now, just
passes the parse information straight to HTML.c for rendering. In
this scheme, HTML.c wouldn't render anything, just create an internal
representation of the document which would then be rendered by a seperate
mechanism which can then take advantage of full knowledge about the
parse-tree.
Does that make more sense?
--
rob partington % [EMAIL PROTECTED] % http://lynx.browser.org/
