xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Xmlgraphics Wiki] Trivial Update of "XmlGraphicsCommonComponents" by WilliamK31
Date Mon, 27 Feb 2012 19:59:39 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Xmlgraphics Wiki" for change notification.

The "XmlGraphicsCommonComponents" page has been changed by WilliamK31:

  = XML Graphics common components =
  == The problem ==
  The FOP codebase contains two Batik transcoders for PDF and PostScript which can be used
independently of FOP and are distributed with Batik. The Batik team should be empowered to
help maintain these transcoders, for example, after changes in Batik itself. Since Batik and
FOP are both implementing an XML standard that creates graphical output there is some overlap
between the two efforts. Last but not least, a Batik release didn't involve a FOP release
until now which is something that must change.
  == The idea ==
  The idea now is to create a common area where the parts of common interest between the two
subprojects are jointly developed and maintained. XML Graphics Commons will deliver a set
of well-defined libraries of which some might provide some supporting tools (such as the TTFReader
and the PFMReader, but which will eventually vanish when they are not needed anymore). Other
potentially reusable software like utilities for build support, ant tasks, plugins for IDEs,
test frameworks and data files might also qualify for finding a home in XML Graphics Commons.
  === Benefits ===
   * Clear dependencies
   * More structured codebase
   * Easier for newbies to contribute to certain parts (They are afraid now of the big blob
of code)
@@ -20, +15 @@

   * Faciliating collaboration with "competing" projects like FOray and Folio, i.e. work together
on undisputed parts of an XSL-FO processor.
  == The plan ==
  === Common repository ===
  For the joint operations we need a common repository. Since we now have migrated both subprojects
to Subversion we are in a good starting position for this.
  === Parts affected in FOP ===
   * PDF transcoder (org.apache.fop.svg)
@@ -55, +47 @@

  [3] During the move it should be tried to remove this dependency, i.e. no logging at all
in the basic shared components.
  === Parts affected in Batik ===
  The transcoders depend on several packages inside Batik. Obviously, we can't create a clean
hierarchy without dependencies on Batik, at least for the PDF and PS transcoders. But we should
do that for the parts where this is possible (PDF lib, fonts, images etc.).
  '''Possible components coming from Batik:'''
@@ -67, +58 @@

   * ...
  === Organization and naming ===
- ==== Naming the individual parts  ====
+ ==== Naming the individual parts ====
  ''Apache XML Graphics Commons''
   * xmlgraphics-commons-pdf (PDF library)
@@ -82, +71 @@

   * xmlgraphics-commons-rtf (RTF library)
  ==== Layout in SVN ====
    +-- commons
          +-- branches
@@ -114, +101 @@

          +-- tags
          +-- trunk
    +-- site
   * In this scenario, the PDF and PS transcoders are transferred to the Batik subproject
under their repository.
@@ -126, +111 @@

   * All releases are always coordinated on the project level (i.e. on level Apache XML Graphics).
  === Notes on additional use cases for the separated components ===
-  * PDFDocumentGraphics2D and PSDocumentGraphics2D can be used to create streamed print services
for JPS which would allow arbitrary Java applications to create PDF and PostScript by simply
printing to JPS.
+  * PDFDocumentGraphics2D and PSDocumentGraphics2D can be used to create streamed print services
for JPS which would allow arbitrary Java applications to create PDF and PostScript by simply
printing to JPS.[[http://www.forfait-mobile.info|forfait mobile]]
   * The PDF library could be used to create PDF documents from scratch (iText is probably
better suited for that).
   * The PDF library could be extended to modify existing documents (same comment as above)
   * The PS library code could be extended to support PostScript post-processing.
   * The RTF library is reported to be used separately. There is desire for a separate JAR
with only the RTF generation code.
  === work items ===
   * Move Batik and FOP to Subversion.

To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org

View raw message