You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by bu...@apache.org on 2002/11/19 15:04:24 UTC
DO NOT REPLY [Bug 14679] New: -
Pluggable renderers
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: fop-dev@xml.apache.org
ReportedBy: tim@tim-landscheidt.de
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: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org