Fopdevs,
I have been hacking away at the documentation, and in particular at the
alt.properties implemetation description. As part of that, I have tried
to develop a framework with an integrated code view. At this stage it
is fairly rudimentary and messy, and does not integrate at all well wi
J,
J.Pietschmann wrote:
Clay Leeds wrote:
Not trying to belabor a point, just trying to get understanding of how
this all works. I would think that JVM only has to start once during a
processing instance.
This is correct. The start and warp-up overhead accounts for the
difference between the
Clay Leeds wrote:
Not trying to belabor a point, just trying to get understanding of how
this all works. I would think that JVM only has to start once during a
processing instance.
This is correct. The start and warp-up overhead accounts for the
difference between the 2s for page rendering and
A couple of new functions to FOP's PDF rendering:
o SVG's and images as page fore-/backgrounds with transparency control
o SVG rendering as image
o Image resolution control by the user
o Caching on the PDF way: store/write a resource once - reuse it
o Open Actions
These add-ons are programmed as
Hi,
The XMLRenderer doesn't seem to print the body portion
at least in some cases. The problem seems to be in
public void renderPage(Page page);
where,
if (body!= null)
body.render(this);
is missing.
Adding these two lines after
if (end != null)
end.re
Jeremias Maerki wrote:
[..]
I'll put your fix in but I can't guarantee that it'll be before
Christian does the release.
Bug #15936 is still an open issue ...
I've mixed feelings about committing patches at this stage of the
release but it's ok if they are as simple as this one.
(I'll just thi
If you transform your XML to PDF using fop.bat you're starting one JVM.
If you're calling the Xalan command line to generate the XSL-FO and then
you invoke fop.bat with -fo to get the PDF, then you're starting two
JVMs. It is very strange that it seems to be faster to start two VMs
than to do the t
Jeremias,
Jeremias Maerki wrote:
As Jörg said, you have to take JVM startup into account. That makes the
whole thing relatively unpredictable. Measuring times from batch files
is ok to get a general idea but not for investigating details. For that
you have to write a Java program and execute the
> >The asap rendering is mostly done, we still need to bring back many of
> >the renderers.
>
> I suppose you mean the PDFRenderer is mostly done.
Yes.
I should probably expand on that topic a bit.
The layout creates an area tree which consists of pages. As each page is
created by the layout th
>The asap rendering is mostly done, we still need to bring back many of
>the renderers.
I suppose you mean the PDFRenderer is mostly done.
>The "SAX" input is really about processing the layout as the fo comes
>in. This depends mainly on the FO tree and the layout system.
What up-to-date sourc
>The asap rendering is mostly done, we still need to bring back many of
>the renderers.
I suppose you mean the PDFRenderer is mostly done.
>The "SAX" input is really about processing the layout as the fo comes
>in. This depends mainly on the FO tree and the layout system.What
up-to-date source
pbwest 2003/01/24 01:36:49
Modified:src/documentation/content/design/alt.design/properties
index.html
Log:
Changed frame configuration.
Revision ChangesPath
1.2 +9 -53
xml-fop/src/documentation/content/design/alt.design/properties/index
pbwest 2003/01/24 01:34:51
Modified:src/documentation/content/design/alt.design
alt-design-frameset.html logo.html
Log:
Changed frame configuration.
Revision ChangesPath
1.3 +9 -53
xml-fop/src/documentation/content/design/alt.design/alt
13 matches
Mail list logo
