HEAD does not compile under jdk 1.5
Current source code does not compile under J2SE 5 due to the use of variables called "enum". This is now a reserved word. These errors are inside the org.apache.fop.render.rtf package. thank you -- bobby abraham
Re: AreaFactory patch
I'd rather we have pluggable LayoutManagers -- 1.0's emphasis and I think our previous agreement with Finn/Simon -- than have pluggable Area objects (where much of layout used to be in 0.20.5.) I'm not sure if Fop can realistically handle both at this time. As for complexity, in our LM's, with Tybor's proposed change, instead of just: curBlockArea = new Block(); we would now have: curBlockArea = (Block) fobj.getUserAgent(). getAreaFactory().create(Block.class, fobj, this); instead of: viewportBlockArea = new BlockViewport(); we would now have: viewportBlockArea = (BlockViewport) fobj.getUserAgent() .getAreaFactory().create (BlockViewport.class, fobj, this); over and over again. The question here seems to be: should we add this additional complexity to our system *now* so Tybor doesn't need to rewrite code every week he does a cvs update? Or have him tolerate it until 1.0 is out (when presumably, he can rely on a production release and not need to update every week.) Personally speaking, I am much more amenable to adding some complexity (LM Makers, for example, or opening up our validation) if it helps out Finn's work, because of the sheer weight of contributions he adds to Fop. (We slow him down, we slow down Fop.) Making these changes for someone who isn't submitting contributions, however, is less of a concern for me. If a user is going to propose a change that would slow down system development, we should be getting some work to compensate for it, at least during this time while we are still building the system. My inclination is to have him place this patch in Bugzilla, and let's wait until we have others requesting it (vs. those who would rather have LM's pluggable.) In the meantime, I think it would be best for everyone to keep layout as simple as we can until it is done. I am open to others' opinions however. Glen --- Tibor Vyletel <[EMAIL PROTECTED]> wrote: > Hello Fopsters, > > I have attached first phase (a working example) of > the refactoring I was > talking about in my previous mails. Please let me > know, if this change is > acceptable for you. If it is, I will finish it > afterwards. >
AreaFactory patch
Hello Fopsters, I have attached first phase (a working example) of the refactoring I was talking about in my previous mails. Please let me know, if this change is acceptable for you. If it is, I will finish it afterwards. Change description: 1) new interface: org.apache.fop.area.AreaFactory & default implementation: org.apache.fop.area.DefaultAreaFactory - new definition how new areas should be created and accessed. 2) FOUserAgent - addition of setAreaFactory(AreaFactory) & AreaFactory getAreaFactor() methods - configuration for new "feature" 3) LayoutManagers - in several managers (in fact, in those I had had my private code) area instantiation was changed to proposed factory pattern. Best regards, Tibor Vyletel ICQ# 79458455 AreaFactoryPhase1.patch Description: Binary data
[GUMP@brutus]: Project xml-fop (in module xml-fop) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xml-fop has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - xml-fop : XSL-FO (Formatting Objects) processor Full details are available at: http://brutus.apache.org/gump/public/xml-fop/xml-fop/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [fop.jar] identifier set to project name -INFO- Made directory [/usr/local/gump/public/workspace/xml-fop/build/classes] -INFO- Made directory [/usr/local/gump/public/workspace/xml-fop/build/test-classes] -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/xml-fop/xml-fop/gump_work/build_xml-fop_xml-fop.html Work Name: build_xml-fop_xml-fop (Type: Build) Work ended in a state of : Failed Elapsed: 30 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only gump [Working Directory: /usr/local/gump/public/workspace/xml-fop] CLASSPATH : /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/xml-fop/build/classes:/usr/local/gump/public/workspace/xml-fop/build/test-classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-stylebook.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/xml-batik/batik-31102004/lib/batik-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-31102004/lib/batik-swing.jar:/usr/local/gump/public/workspace/xml-batik/batik-31102004/lib/batik-css.jar:/usr/local/gump/public/workspace/xml-batik/batik-31102004/lib/batik-bridge.jar:/usr/local/gump/public/workspace/xml-batik/batik-31102004/lib/batik-xml.jar:/usr/local/gump/public/workspace/xml-batik/batik-31102004/lib/batik-svg-dom.jar:/usr/local/gump/public/workspace/xml-batik/batik-31102004/lib/batik-awt-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-31102004/lib/batik-transcoder.jar:/usr/local/gump/public/workspace/xml-batik/batik-31102004/lib/batik-gui-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-31102004/lib/batik-dom.jar:/usr/local/gump/public/workspace/xml-batik/batik-31102004/lib/batik-ext.jar:/usr/local/gump/public/workspace/xml-batik/batik-31102004/lib/batik-svggen.jar:/usr/local/gump/public/workspace/xml-batik/batik-31102004/lib/batik-parser.jar:/usr/local/gump/public/workspace/xml-batik/batik-31102004/lib/batik-extension.jar:/usr/local/gump/public/workspace/xml-batik/batik-31102004/lib/batik-gvt.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-31102004.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-31102004.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-31102004.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-31102004.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jakarta-commons/io/dist/jakarta-commons-io-31102004.jar:/usr/local/gump/public/workspace/jfor/dist/lib/jfor-31102004.jar:/usr/local/gump/public/workspace/jakarta-servletapi/dist/lib/servlet.jar - junit: [javac] Compiling 31 source files to /home/gump/workspaces2/public/workspace/xml-fop/build/test-classes [javac] This version of java does not support the classic compiler; upgrading to modern [javac] /home/gump/workspaces2/public/workspace/xml-fop/test/java/org/apache/fop/util/ASCII85InputStreamTestCase.java:25: warning: org.apac
Bug report for Fop [2004/10/31]
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned|
| | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) |
| | +-+
| | | Severity: BLK=Blocker CRI=CriticalMAJ=Major |
| | | MIN=Minor NOR=Normal ENH=Enhancement |
| | | +-+
| | | | Date Posted |
| | | | +--+
| | | | | Description |
| | | | | |
| 635|Opn|Nor|2001-02-18|Doesn't support id= attribute in fo:page-sequence |
| 953|Opn|Nor|2001-03-12|Incorrect hyperlinks area rendering in justified t|
| 1063|New|Nor|2001-03-21|fop does not handle large fo files|
| 1180|New|Maj|2001-04-02|Problem with monospaced font |
| 1859|Opn|Min|2001-05-22|org.apache.fop.apps.Driver.reset() doesn't fully r|
| 1998|New|Nor|2001-06-05|linefeed-treatment not understood |
| 2150|Ass|Maj|2001-06-13|New page with a table-header but without any tabl|
| 2475|Ass|Nor|2001-07-06|Borders don't appear to work in |
| 2740|New|Maj|2001-07-23|multi-page tables sometimes render badly |
| 2909|New|Maj|2001-07-30|Gradient render error |
| 2964|Ass|Nor|2001-08-02|problems with height of cells in tables |
| 2988|New|Maj|2001-08-03|0.19: list-item-label does not stick to list-item-|
| 3044|Ass|Maj|2001-08-08|keep-together not functioning |
| 3280|New|Nor|2001-08-27|PCL Renderer doesn't work |
| 3305|Opn|Nor|2001-08-28|list-block overlapping footnote body |
| 3497|New|Maj|2001-09-07|id already exists error when using span="all" attr|
| 3824|New|Blk|2001-09-25|MIF option with tables|
| 4030|New|Nor|2001-10-08|IOException creating Postscript with graphics on S|
| 4126|New|Nor|2001-10-12|FontState.width() returns pts instead of millipts |
| 4226|New|Nor|2001-10-17|The orphans property doesn't seem to work |
| 4388|New|Nor|2001-10-24|Nullpointer exception in the construction of new D|
| 4415|New|Nor|2001-10-25|scaling="uniform" does not work on images... |
| 4510|New|Nor|2001-10-30|fo:inline common properties ignored? |
| 4535|New|Maj|2001-10-31|PCL renderer 1.13 not rendering SVG |
| 4767|New|Nor|2001-11-09|SVG text is distored in PDF output|
| 5001|New|Nor|2001-11-21|content-width and content-height ignored? |
| 5010|New|Enh|2001-11-21|Better error reporting needed |
| 5124|New|Maj|2001-11-27|fo:block-container is not rendered properly using |
| 5335|Opn|Min|2001-12-10|Text with embedded CID fonts not retrievable from |
| 5655|Ass|Nor|2002-01-02|text-decoration cannot take multiple values |
| 6094|Opn|Maj|2002-01-29|0.20.3rc hangs in endless loop|
| 6237|Opn|Nor|2002-02-05|fi (fi ligature) produces a "sharp"? |
| 6305|New|Nor|2002-02-07|Using fo:table-and-caption results in empty output|
| 6427|New|Enh|2002-02-13|Adding additional Type 1 fonts problem|
| 6437|New|Maj|2002-02-13|Tables without fo:table-column don't render |
| 6483|New|Nor|2002-02-15|Table, Loop, "footer could not fit on page, moving|
| 6844|New|Nor|2002-03-04|No line breaks inserted in list-item-label|
| 6918|New|Enh|2002-03-06|reference-orientation has no effect |
| 6997|New|Nor|2002-03-09|[PATCH] Row-spanned row data breaks over a page wi|
| 7140|New|Enh|2002-03-15|page-position attribute set to "last" on condition|
| 7241|New|Nor|2002-03-19|keep-with-previous, keep-with-next only working on|
| 7283|New|Nor|2002-03-20|Table border misaligned when using margin-left in |
| 7337|New|Nor|2002-03-21|border around external image leaves empty space |
| 7487|New|Nor|2002-03-26|break-before="page" for table inserts empty page |
| 7496|New|Nor|2002-03-26|The table header borders are not adjusted to the b|
| 7525|New|Cri|2002-03-27|table with spans inside a list-block |
| 7919|New|Cri|2002-04-10|problem to use attribute linefeed-treatment and li|
| 8003|Ass|Maj|2002-04-12|FopImageFactory never releases cached images |
| 8050|New|Nor|2002-04-13|Soft hyphen () is not handled properly |
| 8321|New|Nor|2002-04-19|from-parent('width') returns 0 for nested tables |
| 8463|New|Nor|2002-04-24|SVG clipping in external.fo example doc when rende|
| 8767|Ass|Min|2002-05-03|Image
Form Extension
Hi FOP devs, I' ve developed a form extension for XSL-FO for an university project. It's an extension to FO like the fox extensions. With it you can declare and define the usual form elements like edit fields, radio buttons, check boxes, combo boxes, list boxes, comment fields and buttons. They are inserted into a document as inline objects, so that they flow like normal text. As a proof of concept I've extended fop-0.20.5 to support my form extension. I'm using the system around ExtensionObj to make fop understand my elements and I've extended the PDFRenderer to generate PDF documents that contain forms, that can be filled out and submitted just like normal HTML forms. At the moment the module for fop consists of a jar archive with the classes and a new batch file to start the processing (I'm not using the fop class as a starter, because I need to create a different renderer). The system works so far and is able to generate all of the form elements named above. Submit and reset buttons work as they're supposed to. I didn't test every layout situation for the form elements, so it might produce unexpected layout in some cases. As I said it's a proof of concept implementation and not a final product. The reason why I'm announcing this is that I will finish the project in a couple of days and I don't think I will develop the form extension any further. Maybe someone will find the sources usefull as a starting point or is even willing to develop it further. The sources and the precompiled jar archive can be found at my homepage [1]. I've also got an example fo document with my extension there, together with the resulting PDF file. So anyone who's interested can take a quick look at it. The paper I'm writing on this project will be released in couple of days (in German though, Studienarbeit) together with a little documentation on the form extension in English. I just wanted to let you know. If you have any questions, just ask me. Any feedback is welcome. Cheers, Florian Hecht P.S.: should I also post this on fop-user? [1] http://wwwstud.ira.uka.de/~s_hecht/
Fw: Apache PMCs: ApacheCon notice
I'm simply forwarding this to you guys. Clay, would you please try to take care of this for the FOP website? Is there anyone from our two projects who will be there? (Without the right president in place and without someone paying for a ticket to fly over, I won't be there. ;-) Looking forward to the next ApacheCon Europe...) Forwarded by Jeremias Maerki <[EMAIL PROTECTED]> --- Original Message --- From:Rodent of Unusual Size <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: Apache Software Foundation conference committee <[EMAIL PROTECTED]> Date:Sun, 31 Oct 2004 09:24:47 -0500 Subject: Apache PMCs: ApacheCon notice -BEGIN PGP SIGNED MESSAGE- Greetings, O ASF PMC. Yes, this is being sent to all of the ASF PMCs, and it has to do with ApacheCon. Two items: Numbah One: It has been noticed that many of the Foundation's own projects don't have any sort of link or advert about ApacheCon on their front pages. I am here to request and exhort that you change this situation immediately, if not sooner. We need all the press we can get. Please put something like this on your front page 'above the fold': http://ApacheCon.Com/2004/US/"; >http://ApacheCon.Com/2004/US/logos/logo_only.gif"; width="170" height="100" alt="ApacheCon!" title="Come to ApacheCon!" border="0" /> Similarly, please let your committers know about the 'ASF committer' logo, and ask them to put a similar link to ApacheCon on *their* sites using 'asf_committer.gif' instead of 'logo_only.gif'. I'm attaching both of these logos to encourage wide dissemination. There are other logos available at http://ApacheCon.Com/2004/US/logos/ (but obviously not all are really for general consumption). Item Numbah Two: Not all of the ASF projects are represented at ApacheCon by having sessions or BOFs scheduled. We (the ASF concom) *very* much want *all* projects to get *lots* of attention from ApacheCon attendees. To that end, I'm asking the PMCs to maybe find out whom from their projects will be at the conference and might be able to wear a button like 'Ask Me About Apache Foo!' Or maybe have a stack of one-page sheets about each of some/many/most/all of the projects available at the registration table, or around during the reception, or whatever. I know, I know -- that's documentation. Yggh. Nevertheless, ApacheCon represents a golden opportunity to increase awareness of and mindshare about your project. *Please* consider taking advantage of it! If you'd like some 'Ask Me About Apache !' buttons, please let us know the details (what 'foo' is, what colours are preferred [no guarantees], and how many) in a message to [EMAIL PROTECTED] I can't guarantee that we'll be able to make them, but we'll try. Oh, and the names of the people who have volunteered to wear 'em would be good, too, so we can try to make the contracted registration people aware that there's a button for Jean D'Oh. Or we could just get a bunch and let people pick 'em up. Thanks! - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBQYT1rprNPMCpn3XdAQHd2gQAp/0qTiUg7XtGjcgPfZWAzc90YmR3txW6 y/iZM7IFkYT+f17ptWnXo3cVTswyxF61xuvg17+IC/volrOFAhz8IhbcZPCJ60RR LSucNFpLML3CvP8JLkwd0eRFlMcPuhR+dyGuSptEEeGXY/aszdXX/fBV2Zbdw5d4 Xo4lJoYAzd8= =iY8p -END PGP SIGNATURE- - Original Message Ends Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
