gmazza 2003/08/28 16:43:50
Modified:src/java/org/apache/fop/render/awt AWTRenderer.java
src/java/org/apache/fop/viewer PreviewDialog.java
Log:
(Very) initial steps in activating AWTRenderer PreviewDialog in 1.0 (creating
outer page).
Revision ChangesPath
From: Victor Mote [EMAIL PROTECTED]
FOP Developers:
I just committed a change (for the FO isolation work) that may have broken
my general rule of not changing the substance of what is going on in the
code. The fo/pagination/StaticContent stored a reference to a
StaticContentLayoutManager and
FOP Devs,
there have been a couple of questions on use of block-containers and
absolute positioning this week. I couldnt see anything obvious on the
website, but I may have missed it. In either case I thought it would be
useful to add a few words about block-container to the compliance page. I
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22811.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Chris Bowditch wrote:
just a thought on this. The previous behaviour of the
StaticContent LM that
you describe above is like a singleton. Isnt the reason
StaticContent LM is
behaving like a singleton, because static content should only be laid out
one time? It may not change behaviour if
Well, the actual layout for static content can obviously differ
from page to page because of markers and page numbers.
However, constructing a LM is expensive, and in the original
code I wrote a new LM would have been created for each page if
the FO didn't keep it, which would have cause unwanted
Joerg Pietschmann wrote:
Well, the actual layout for static content can obviously differ
from page to page because of markers and page numbers.
However, constructing a LM is expensive, and in the original
code I wrote a new LM would have been created for each page if
the FO didn't keep it,
vmote 2003/08/29 13:02:11
Modified:src/java/org/apache/fop/layoutmgr PageLayoutManager.java
Log:
store a collection of StaticContentLayoutManager objects, keyed by flow-name, to be
used instead of creating new ones each time one is needed
Revision ChangesPath
1.18
Victor Mote wrote:
OK, that is good information. Essentially, I have caused that unwanted
overhead. So probably what I should do is store the StaticContentLM
reference in the related RegionLM. I'll work on that.
Regions don't have LMs, so I created a HashMap of the StaticContentLMs in
the
