Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Xmlgraphics-fop Wiki" 
for change notification.

The following page has been changed by JeremiasMaerki:
http://wiki.apache.org/xmlgraphics-fop/AreaTreeIntermediateXml/NewDesign

The comment on the change is:
Fixed a typo and updated design graphic to reflect text

------------------------------------------------------------------------------
  
  == IFPainter design ==
  
- IFPainter (working title, better suggestions welcome!) is a central 
interface, like Renderer. There's one implementation for each output format 
that is useful in the context of the intermediate format (probably includes all 
current renderers except text. most important are: PostScript, AFP and PCL). 
Ideally, the IFPainter interface is a direct equivalent to the possible SAX 
stream for the new IF format, i.e. it is possible to convert between IFPainter 
and the IF-NG SAX stream with no losses. The IFContentHandler in the graphic 
above would convert the SAX stream to IPPainter calls and a special IFPainter 
implementation used by IFRenderer could convert the calls to the SAX stream. 
That way, the IFRenderer could actually render to an IFPainter without the 
detour over XML.
+ IFPainter (working title, better suggestions welcome!) is a central 
interface, like Renderer. There's one implementation for each output format 
that is useful in the context of the intermediate format (probably includes all 
current renderers except text. most important are: PostScript, AFP and PCL). 
Ideally, the IFPainter interface is a direct equivalent to the possible SAX 
stream for the new IF format, i.e. it is possible to convert between IFPainter 
and the IF-NG SAX stream with no losses. The IFContentHandler in the graphic 
above would convert the SAX stream to IFPainter calls and a special IFPainter 
implementation used by IFRenderer could convert the calls to the SAX stream. 
That way, the IFRenderer could actually render to an IFPainter without the 
detour over XML.
  
  The IFPainter interface is not fully designed, yet, so the following is just 
to give an idea what it could look like (all methods will probably throw 
SAXException):
  

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

Reply via email to