Aside from my low opinion of SAX for process coupling, there should be 
no need for communication back from the renderer.  The Area Tree should 
just give orders to the renderer.  All of the layout decisions have been 
made by the time the Area Tree is constructed.  The feedback is within 
the layout process, and the particulars of that are the cause of much 
wailing and gnashing of teeth.


Bertrand Delacretaz wrote:

>On Thursday 14 March 2002 09:27, Nicola Ken Barozzi wrote:
>>. . .
>>I think that a SAXrenderer could be the solution. SAX is based on
>>calling a method when a tag begin-content-end is reached. It can be
>>used to communicate the Area Tree to the renderer in a clean way,
>>whith a standard interface.
>>. . .
>Won't work I think, print-based layout (as opposed to structure-based) 
>requires two-way communication between the layout engine and the 
>renderer (to compute the width text runs, for example).

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to