DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14679>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14679 Pluggable renderers Summary: Pluggable renderers Product: Fop Version: all Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: general AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Playing around with gcj the other day, I noticed fop is not gcj-"compatible" (yet) due to its AWT renderer that requires swing classes. Not having studied the redesign code in detail, I'd like to propose (if not already part of the master plan) to source out the renderers in small modules so that not only limitations in the Java VM can be avoided :-) but also to follow the KISS principle when your use case only requires PDF (or RTF or ...) output. Another idea (from a "./configure && make install" background) would be to have "options" "--enable-pdf", "--enable-ps", "--enable-rtf" & Co. to the build process that determine which renderers are to be included. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
