Return-Path: Delivered-To: apmail-xmlgraphics-commits-archive@www.apache.org Received: (qmail 86869 invoked from network); 18 Jun 2010 11:53:32 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 18 Jun 2010 11:53:32 -0000 Received: (qmail 1663 invoked by uid 500); 18 Jun 2010 11:53:32 -0000 Mailing-List: contact commits-help@xmlgraphics.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@xmlgraphics.apache.org Delivered-To: mailing list commits@xmlgraphics.apache.org Received: (qmail 1645 invoked by uid 500); 18 Jun 2010 11:53:32 -0000 Delivered-To: apmail-xmlgraphics-site-commits@xmlgraphics.apache.org Received: (qmail 1639 invoked by uid 99); 18 Jun 2010 11:53:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Jun 2010 11:53:32 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Jun 2010 11:53:26 +0000 Received: by eris.apache.org (Postfix, from userid 65534) id 1A87D23889F1; Fri, 18 Jun 2010 11:52:39 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r955955 [3/8] - in /xmlgraphics/site/deploy/fop: ./ dev/ trunk/ Date: Fri, 18 Jun 2010 11:52:38 -0000 To: site-commits@xmlgraphics.apache.org From: psancho@apache.org X-Mailer: svnmailer-1.0.8 Message-Id: <20100618115239.1A87D23889F1@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Modified: xmlgraphics/site/deploy/fop/compliance.pdf URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/compliance.pdf?rev=955955&r1=955954&r2=955955&view=diff ============================================================================== Files xmlgraphics/site/deploy/fop/compliance.pdf (original) and xmlgraphics/site/deploy/fop/compliance.pdf Fri Jun 18 11:52:37 2010 differ Modified: xmlgraphics/site/deploy/fop/compliance.xml URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/compliance.xml?rev=955955&r1=955954&r2=955955&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/compliance.xml (original) +++ xmlgraphics/site/deploy/fop/compliance.xml Fri Jun 18 11:52:37 2010 @@ -1,2 +1,2 @@ [... 4 lines stripped ...] Modified: xmlgraphics/site/deploy/fop/dev/extensions.html URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/dev/extensions.html?rev=955955&r1=955954&r2=955955&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/dev/extensions.html (original) +++ xmlgraphics/site/deploy/fop/dev/extensions.html Fri Jun 18 11:52:37 2010 @@ -1,352 +1,352 @@ - - - - - - - -FOP Development: Adding an Extension - - - - - - - - - -
- -
- - - - - - - - - - - - -
-
-
-
- -
- - -
- - - - - - - -
- - -
Font size: -   -   -   -
-

FOP Development: Adding an Extension

-
-
- -
-
- - -

Overview

-
-

For documentation of standard FOP extensions, see the User FOP Extensions document.

-

-If the default funtionality of FOP needs to be extended for -some reason then you can write an extension. -

-

There are three types of extensions possible:

-
    - -
  • An output document extension such as the PDF bookmarks
  • - -
  • an instream-foreign-object extensions such as SVG
  • - -
  • an fo extension that creates an area in the area tree where normal xsl:fo is not possible
  • - -
-
- - -

Adding Your Own

-
-

-To add your own extension you need to do the following things. -

-
    - -
  1. Write code that implements your extension functionality. The easiest place to -start is by looking at the code in org.apache.fop.extension, and by looking at the examples in the examples directory.
  2. - -
  3. Create a class that implements the org.apache.fop.fo.ElementMapping interface. ElementMapping is a hashmap of all of the elements in a particular namespace, which makes it easier for FOP to create a different object for each element. -ElementMapping objects are static to save on memory. -They are loaded by FOP when parsing starts to validate input.
  4. - -
  5. Create the following file: "/META-INF/services/org.apache.fop.fo.ElementMapping", which should contain the fully qualified classname of your ElementMapping implementation class.
  6. - -
  7. Create a jar file containing all of the above files.
  8. - -
  9. Create your XSL-FO file with the extra XML data embedded in the file with the -correct name space. -The examples for SVG and pdfoutline.fo show how this can be done. -The pdf documents on the FOP site use this extension. -See also Examples for more examples.
  10. - -
  11. Put your jar file in the classpath
  12. - -
  13. Run FOP using your XSL-FO file as input.
  14. - -
-
- - - version 911792 -
- -
 
-
- - - + + + + + + + +FOP Development: Adding an Extension + + + + + + + + + +
+ +
+ + + + + + + + + + + + +
+
+
+
+ +
+ + +
+ + + + + + + +
+ + +
Font size: +   +   +   +
+

FOP Development: Adding an Extension

+
+
+ +
+
+ + +

Overview

+
+

For documentation of standard FOP extensions, see the User FOP Extensions document.

+

+If the default funtionality of FOP needs to be extended for +some reason then you can write an extension. +

+

There are three types of extensions possible:

+
    + +
  • An output document extension such as the PDF bookmarks
  • + +
  • an instream-foreign-object extensions such as SVG
  • + +
  • an fo extension that creates an area in the area tree where normal xsl:fo is not possible
  • + +
+
+ + +

Adding Your Own

+
+

+To add your own extension you need to do the following things. +

+
    + +
  1. Write code that implements your extension functionality. The easiest place to +start is by looking at the code in org.apache.fop.fo.extensions, and by looking at the examples in the examples directory.
  2. + +
  3. Create a class that extends the abstract org.apache.fop.fo.ElementMapping class. ElementMapping is a hashmap of all of the elements in a particular namespace, which makes it easier for FOP to create a different object for each element. +ElementMapping objects are static to save on memory. +They are loaded by FOP when parsing starts to validate input.
  4. + +
  5. Create the following file: "/META-INF/services/org.apache.fop.fo.ElementMapping", which should contain the fully qualified classname of your ElementMapping implementation class.
  6. + +
  7. Create a jar file containing all of the above files.
  8. + +
  9. Create your XSL-FO file with the extra XML data embedded in the file with the +correct name space. +The examples for SVG and pdfoutline.fo show how this can be done. +The pdf documents on the FOP site use this extension. +See also Examples for more examples.
  10. + +
  11. Put your jar file in the classpath
  12. + +
  13. Run FOP using your XSL-FO file as input.
  14. + +
+
+ + + version 955915 +
+ +
 
+
+ + + Modified: xmlgraphics/site/deploy/fop/dev/extensions.pdf URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/dev/extensions.pdf?rev=955955&r1=955954&r2=955955&view=diff ============================================================================== Files xmlgraphics/site/deploy/fop/dev/extensions.pdf (original) and xmlgraphics/site/deploy/fop/dev/extensions.pdf Fri Jun 18 11:52:37 2010 differ Modified: xmlgraphics/site/deploy/fop/dev/extensions.xml URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/dev/extensions.xml?rev=955955&r1=955954&r2=955955&view=diff ============================================================================== --- xmlgraphics/site/deploy/fop/dev/extensions.xml (original) +++ xmlgraphics/site/deploy/fop/dev/extensions.xml Fri Jun 18 11:52:37 2010 @@ -17,7 +17,7 @@
FOP Development: Adding an Extension - $Revision: 911792 $ + $Revision: 955915 $
@@ -41,8 +41,8 @@ To add your own extension you need to do

  1. Write code that implements your extension functionality. The easiest place to -start is by looking at the code in org.apache.fop.extension, and by looking at the examples in the examples directory.
  2. -
  3. Create a class that implements the org.apache.fop.fo.ElementMapping interface. ElementMapping is a hashmap of all of the elements in a particular namespace, which makes it easier for FOP to create a different object for each element. +start is by looking at the code in org.apache.fop.fo.extensions, and by looking at the examples in the examples directory.
  4. +
  5. Create a class that extends the abstract org.apache.fop.fo.ElementMapping class. ElementMapping is a hashmap of all of the elements in a particular namespace, which makes it easier for FOP to create a different object for each element. ElementMapping objects are static to save on memory. They are loaded by FOP when parsing starts to validate input.
  6. Create the following file: "/META-INF/services/org.apache.fop.fo.ElementMapping", which should contain the fully qualified classname of your ElementMapping implementation class.
  7. @@ -57,4 +57,4 @@ See also E
-
+ \ No newline at end of file --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org For additional commands, e-mail: commits-help@xmlgraphics.apache.org