Re: Dropping Support for Old Renderers
Thanks for that, that helped. This is now done. Thanks, Vincent Jeremias Maerki wrote: Just to have an overview over all output formats: AFP: Painter available AWT: Renderer only at the moment (depends on Java2D) PNG/TIFF: Painter available (depends on Java2D) Java2D: Painter available PCL: Painter available PDF: Painter available Print: Renderer only at the moment (depends on Java2D) PS: Painter available RTF: n/a (Does not use layout engine) TXT: Renderer only AT XML: Renderer only but that has to be like that IF XML: Renderer to Painter adapter present (other painter impls rely on that) Essentially, this means that the renderers for AFP, PCL, PDF and PS can be removed because they are fully replaced by their painter counterparts. All the other renderers have to stay in place: Java2D/AWT/Print, TXT, AT XML, IF XML. AWT, Print and TXT are candidates to be ported to the painter infrastructure. On 17.08.2010 19:57:08 Vincent Hennebert wrote: Ok, no objection to this so I'll proceed with the removal. Thanks, Vincent Vincent Hennebert wrote: Hi, The new rendering architecture based on a streamlined intermediate format and painters has been in place for more than a year now and hasn’t caused any big issue. New features are being added to the painters (PDFDocumentHandler/PDFPainter, PSDocumentHandler/PSPainter, etc.) and usually not backported to the renderers (PDFRenderer, PSRenderer, etc.). Also, the old renderers get in the way when changes and refactorings must be made to the libraries. Therefore, I propose to drop support for the old renderers and remove them from version control. Does anyone have any objection to that? Thanks, Vincent Jeremias Maerki
Re: Dropping Support for Old Renderers
Just to have an overview over all output formats: AFP: Painter available AWT: Renderer only at the moment (depends on Java2D) PNG/TIFF: Painter available (depends on Java2D) Java2D: Painter available PCL: Painter available PDF: Painter available Print: Renderer only at the moment (depends on Java2D) PS: Painter available RTF: n/a (Does not use layout engine) TXT: Renderer only AT XML: Renderer only but that has to be like that IF XML: Renderer to Painter adapter present (other painter impls rely on that) Essentially, this means that the renderers for AFP, PCL, PDF and PS can be removed because they are fully replaced by their painter counterparts. All the other renderers have to stay in place: Java2D/AWT/Print, TXT, AT XML, IF XML. AWT, Print and TXT are candidates to be ported to the painter infrastructure. On 17.08.2010 19:57:08 Vincent Hennebert wrote: Ok, no objection to this so I'll proceed with the removal. Thanks, Vincent Vincent Hennebert wrote: Hi, The new rendering architecture based on a streamlined intermediate format and painters has been in place for more than a year now and hasn’t caused any big issue. New features are being added to the painters (PDFDocumentHandler/PDFPainter, PSDocumentHandler/PSPainter, etc.) and usually not backported to the renderers (PDFRenderer, PSRenderer, etc.). Also, the old renderers get in the way when changes and refactorings must be made to the libraries. Therefore, I propose to drop support for the old renderers and remove them from version control. Does anyone have any objection to that? Thanks, Vincent Jeremias Maerki
Re: Dropping Support for Old Renderers
Ok, no objection to this so I'll proceed with the removal. Thanks, Vincent Vincent Hennebert wrote: Hi, The new rendering architecture based on a streamlined intermediate format and painters has been in place for more than a year now and hasn’t caused any big issue. New features are being added to the painters (PDFDocumentHandler/PDFPainter, PSDocumentHandler/PSPainter, etc.) and usually not backported to the renderers (PDFRenderer, PSRenderer, etc.). Also, the old renderers get in the way when changes and refactorings must be made to the libraries. Therefore, I propose to drop support for the old renderers and remove them from version control. Does anyone have any objection to that? Thanks, Vincent
Re: Dropping Support for Old Renderers
Certainly not from me. So far I was always asked by my clients to add all new features to the Renderer, too. But instead of using the PDFRenderer (for example) directly, one can always use the IFRenderer with PDFDocumentHandler as its backend which should make the transition easier. Maybe it's a bit hard just to remove the classes without some deprecation time, but that's not a hard requirement from my side in this case since usually, users select the output format by MIME type and have been using the new implementations already anyway. It would only affect some advanced users which I think can be expected to deal with that when they upgrade. On 06.08.2010 19:29:06 Vincent Hennebert wrote: Hi, The new rendering architecture based on a streamlined intermediate format and painters has been in place for more than a year now and hasn’t caused any big issue. New features are being added to the painters (PDFDocumentHandler/PDFPainter, PSDocumentHandler/PSPainter, etc.) and usually not backported to the renderers (PDFRenderer, PSRenderer, etc.). Also, the old renderers get in the way when changes and refactorings must be made to the libraries. Therefore, I propose to drop support for the old renderers and remove them from version control. Does anyone have any objection to that? Thanks, Vincent Jeremias Maerki
