Re: orphan - widow
Patrick Andries wrote: What is the status of the orphan and widow control ? It is not implemented in 0.20.3, there is no precise timeline (somewhen this year), it is not all that easy to implement in the current design, and there is no schedule for the redesigned FOP. There may be another maintenance release in the short term, but certainly without orpahns/widows and keeps. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: orphan - widow
OK. thanks, although this is not good news. J.Pietschmann wrote: Patrick Andries wrote: What is the status of the orphan and widow control ? It is not implemented in 0.20.3, there is no precise timeline (somewhen this year), it is not all that easy to implement in the current design, and there is no schedule for the redesigned FOP. There may be another maintenance release in the short term, but certainly without orpahns/widows and keeps. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/viewer PreviewDialog.java
chrisg 02/04/01 11:21:39
Modified:src/org/apache/fop/apps Tag: fop-0_20_2-maintain
AWTStarter.java
src/org/apache/fop/viewer Tag: fop-0_20_2-maintain
PreviewDialog.java
Log:
exit for closing window is only called for the AWTStarter, command line
and not on the window (done by Keiron, synced from trunk)
Revision ChangesPath
No revision
No revision
1.9.2.3 +8 -1 xml-fop/src/org/apache/fop/apps/AWTStarter.java
Index: AWTStarter.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/apps/AWTStarter.java,v
retrieving revision 1.9.2.2
retrieving revision 1.9.2.3
diff -u -r1.9.2.2 -r1.9.2.3
--- AWTStarter.java 27 Mar 2002 19:15:39 - 1.9.2.2
+++ AWTStarter.java 1 Apr 2002 19:21:39 - 1.9.2.3
@@ -1,5 +1,5 @@
/*
- * $Id: AWTStarter.java,v 1.9.2.2 2002/03/27 19:15:39 chrisg Exp $
+ * $Id: AWTStarter.java,v 1.9.2.3 2002/04/01 19:21:39 chrisg Exp $
* Copyright (C) 2001 The Apache Software Foundation. All rights reserved.
* For details on use and redistribution please refer to the
* LICENSE file included with these sources.
@@ -15,6 +15,8 @@
*/
import org.apache.fop.viewer.*;
import org.apache.fop.render.awt.*;
+import java.awt.event.WindowAdapter;
+import java.awt.event.WindowEvent;
import javax.swing.UIManager;
@@ -129,6 +131,11 @@
Translator res) {
PreviewDialog frame = new PreviewDialog(renderer, res);
frame.validate();
+frame.addWindowListener(new WindowAdapter() {
+public void windowClosed(WindowEvent we) {
+System.exit(0);
+}
+});
// center window
Dimension screenSize = Toolkit.getDefaultToolkit().getScreenSize();
No revision
No revision
1.7.2.1 +1 -6 xml-fop/src/org/apache/fop/viewer/PreviewDialog.java
Index: PreviewDialog.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/viewer/PreviewDialog.java,v
retrieving revision 1.7
retrieving revision 1.7.2.1
diff -u -r1.7 -r1.7.2.1
--- PreviewDialog.java30 Jul 2001 20:29:35 - 1.7
+++ PreviewDialog.java1 Apr 2002 19:21:39 - 1.7.2.1
@@ -1,5 +1,5 @@
/*
- * $Id: PreviewDialog.java,v 1.7 2001/07/30 20:29:35 tore Exp $
+ * $Id: PreviewDialog.java,v 1.7.2.1 2002/04/01 19:21:39 chrisg Exp $
* Copyright (C) 2001 The Apache Software Foundation. All rights reserved.
* For details on use and redistribution please refer to the
* LICENSE file included with these sources.
@@ -624,11 +624,6 @@
}
}
}
-}
-
-
-public void dispose() {
-System.exit(0);
}
}// class PreviewDialog
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
why doesn't fop take relative path for external graphic
Hi! I am trying to include an image using external-graphic element. It doesn't seem to take relative path. I don't want to specify the absolute path. Any clues? Thanks in advance Bhawana - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/lib/bin antRun
chrisg 02/04/01 15:48:29 Modified:.Tag: fop-0_20_2-maintain CHANGES build.bat build.sh build.xml contrib/servlet Tag: fop-0_20_2-maintain build.bat build.sh docs/examples Tag: fop-0_20_2-maintain runtests.bat runtests.sh lib/bin Tag: fop-0_20_2-maintain antRun Added: lib Tag: fop-0_20_2-maintain ant-1.4.1.jar Removed: lib Tag: fop-0_20_2-maintain ant-1.3-optional.jar ant.jar Log: Updated ant to version 1.4.1 Revision ChangesPath No revision No revision 1.10.2.10 +2 -1 xml-fop/CHANGES Index: CHANGES === RCS file: /home/cvs/xml-fop/CHANGES,v retrieving revision 1.10.2.9 retrieving revision 1.10.2.10 diff -u -r1.10.2.9 -r1.10.2.10 --- CHANGES 17 Mar 2002 23:37:06 - 1.10.2.9 +++ CHANGES 1 Apr 2002 23:48:28 - 1.10.2.10 @@ -4,7 +4,8 @@ - Moved from org.apache.log.Logger to org.apache.avalon.framework.logger.Logger (this removes dependency from logkit) Submitted by: Michael Gratton [EMAIL PROTECTED] - +- Updated ant to version 1.4.1 (Christian Geisert) + (ant-optional.jar is no longer needed) == Done since 0.20.2 release *** General 1.14.2.4 +1 -1 xml-fop/build.bat Index: build.bat === RCS file: /home/cvs/xml-fop/build.bat,v retrieving revision 1.14.2.3 retrieving revision 1.14.2.4 diff -u -r1.14.2.3 -r1.14.2.4 --- build.bat 17 Mar 2002 23:37:06 - 1.14.2.3 +++ build.bat 1 Apr 2002 23:48:28 - 1.14.2.4 @@ -6,7 +6,7 @@ if %JAVA_HOME% == goto error set LIBDIR=lib -set LOCALCLASSPATH=%JAVA_HOME%\lib\tools.jar;%JAVA_HOME%\lib\classes.zip;%LIBDIR%\ant.jar;%LIBDIR%\ant-1.3-optional.jar;%LIBDIR%\batik.jar;%LIBDIR%\buildtools.jar;%LIBDIR%\xerces-1.2.3.jar;%LIBDIR%\xalan-2.0.0.jar;%LIBDIR%\xalanj1compat.jar;%LIBDIR%\bsf.jar +set LOCALCLASSPATH=%JAVA_HOME%\lib\tools.jar;%JAVA_HOME%\lib\classes.zip;%LIBDIR%\ant-1.4.1.jar;%LIBDIR%\batik.jar;%LIBDIR%\buildtools.jar;%LIBDIR%\xerces-1.2.3.jar;%LIBDIR%\xalan-2.0.0.jar;%LIBDIR%\xalanj1compat.jar;%LIBDIR%\bsf.jar set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\jimi-1.0.jar;%LIBDIR%\avalon-framework-cvs-20020315.jar set ANT_HOME=%LIBDIR% 1.15.2.4 +1 -1 xml-fop/build.sh Index: build.sh === RCS file: /home/cvs/xml-fop/build.sh,v retrieving revision 1.15.2.3 retrieving revision 1.15.2.4 diff -u -r1.15.2.3 -r1.15.2.4 --- build.sh 17 Mar 2002 23:37:06 - 1.15.2.3 +++ build.sh 1 Apr 2002 23:48:28 - 1.15.2.4 @@ -13,7 +13,7 @@ exit 1 fi LIBDIR=lib -LOCALCLASSPATH=$JAVA_HOME/lib/tools.jar:$JAVA_HOME/lib/classes.zip:$LIBDIR/ant.jar:$LIBDIR/ant-1.3-optional.jar:$LIBDIR/batik.jar:$LIBDIR/buildtools.jar:$LIBDIR/xerces-1.2.3.jar:$LIBDIR/xalan-2.0.0.jar:$LIBDIR/xalanj1compat.jar:$LIBDIR/bsf.jar +LOCALCLASSPATH=$JAVA_HOME/lib/tools.jar:$JAVA_HOME/lib/classes.zip:$LIBDIR/ant-1.4.1.jar:$LIBDIR/batik.jar:$LIBDIR/buildtools.jar:$LIBDIR/xerces-1.2.3.jar:$LIBDIR/xalan-2.0.0.jar:$LIBDIR/xalanj1compat.jar:$LIBDIR/bsf.jar LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/jimi-1.0.jar:$LIBDIR/avalon-framework-cvs-20020315.jar ANT_HOME=$LIBDIR 1.44.2.10 +1 -1 xml-fop/build.xml Index: build.xml === RCS file: /home/cvs/xml-fop/build.xml,v retrieving revision 1.44.2.9 retrieving revision 1.44.2.10 diff -u -r1.44.2.9 -r1.44.2.10 --- build.xml 17 Mar 2002 23:37:06 - 1.44.2.9 +++ build.xml 1 Apr 2002 23:48:28 - 1.44.2.10 @@ -141,7 +141,7 @@ include name=lib/batik.LICENSE.txt/ include name=lib/avalon-framework-cvs-20020315.jar/ include name=lib/avalon.LICENSE.txt/ - include name=lib/ant.jar/ + include name=lib/ant-1.4.1.jar/ include name=lib/ant.license.txt/ /fileset No revision No revision 1.1.2.2 +1 -1 xml-fop/contrib/servlet/build.bat Index: build.bat === RCS file: /home/cvs/xml-fop/contrib/servlet/build.bat,v retrieving revision 1.1.2.1 retrieving revision 1.1.2.2 diff -u -r1.1.2.1 -r1.1.2.2 --- build.bat 27 Mar 2002 13:08:53 - 1.1.2.1 +++ build.bat 1 Apr 2002 23:48:28 - 1.1.2.2 @@ -6,7 +6,7 @@ if %JAVA_HOME% == goto error set LIBDIR=../../lib -set
Participating in development
Hi Guys, I want to participate in development of FOP could you guys tell me how do I go about? regards Vaidya THIS E-MAIL MESSAGE ALONG WITH ANY ATTACHMENTS IS INTENDED ONLY FOR THE ADDRESSEE and may contain confidential and privileged information. If the reader of this message is not the intended recipient, you are notified that any dissemination, distribution or copy of this communication is strictly Prohibited. If you have received this message by error, please notify us immediately, return the original mail to the sender and delete the message from your system. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Designing PDF extensions: form fields
I programmed PDF form fields into Fop-0.20.1. PDF form fields have an annotation representation in PDF files with the subtype widget. So I patched the external-link within the renderer code to process form fields. Additionally a PDF fields object had to be added to the PDF stream and a reference to it into the PDF document catalog. So far quite easy. From this experience I see now the design below for PDF plugins (rather plugin than FOP extension, because this is only partially FOP business). Main areas of concern are the external interface and on the other hand general methods provided by FOP to generate valid PDF file structures. When this API is available, features like PDF JavaScript etc. will be easy to implement. Plugins are not allowed to modify any FOP code. XSL:FO will be device-dependent. So users will have to take care of that with XSLT. Hansuli Anderegg, Zurich, Switzerland == EXTERNAL INTERFACE PDF Form Field Example: (1) fo:instream-foreign-object width=50 height=12 (2) FOPplugin type=PDFForm renderClass=PDFDocument renderMethod=addFormField (3) /T (pb1) (3) /FT /Btn (3) /Ff 65536 (3) /H /P /F 4 (3) /BS /W 2 /S /B (3) /MK /BC [ 0 0 0 ] (3) /BG [.7529 .7529 .7529] (3) /CA (Button) /FOPplugin /fo:instream-foreign-object (1) instream-foreign-object asks the FOP formatter for space. PDF RENDERER o The foreign-object method of the PDF renderer is called by FOP - arguments: type, renderer class, renderer method (Strings from 2) and rectangle coordinates, data. o control is passed to the specified class/method in FOPplugin - arguments: rectangle coordinates and unprocessed text of XML element FOPplugin. (3) Just anything: in my case the text in native PDF form syntax from the FOPplugin XML element (transforming PDF form syntax into XML syntax does not make sense unless Adobe switches to XML). XML in case of SVG. Perhaps a differenciation between XML and non-XML data will be helpful. Of course the parser requires valid XML input. Character sets and line endings will have to be looked at. INVOKED METHOD by PDF renderer foreign object invokes in turn o special, separate plugin method(s) (most likely added to PDFDocument class) - the plugin has to setup his PDF objects, keep track of his object references. FOP has to enable the plugin to insert PDF objects by an API most likely to be implemented in the PDFDocument class. GENERAL PDFDocument METHODS provided by FOP - request a PDF object (including trailer objects) with ID and XREF maintenance - add entries/PDF reference ID's to catalog (outline requires a catalog entry too) Basically this means providing external interfaces to the PDF package. Not so easy while keeping PDF integrity. __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
