You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-commits@xmlgraphics.apache.org by je...@apache.org on 2005/02/10 13:52:35 UTC
cvs commit: xml-fop/test/layoutengine/testcases normal-breaking4.xml
jeremias 2005/02/10 04:52:35
Modified: test/layoutengine/testcases normal-breaking4.xml
Log:
Adding an additional block at the end to see if a new block would behave differently.
Revision Changes Path
1.2 +2 -1 xml-fop/test/layoutengine/testcases/normal-breaking4.xml
Index: normal-breaking4.xml
===================================================================
RCS file: /home/cvs/xml-fop/test/layoutengine/testcases/normal-breaking4.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- normal-breaking4.xml 10 Feb 2005 12:50:07 -0000 1.1
+++ normal-breaking4.xml 10 Feb 2005 12:52:35 -0000 1.2
@@ -45,6 +45,7 @@
Apache FOP is a great tool to create PDF documents with.
Apache FOP is a great tool to create PDF documents with.
</fo:block>
+ <fo:block background-color="yellow">last line in new block</fo:block>
</fo:flow>
</fo:page-sequence>
</fo:root>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-cvs-help@xml.apache.org
page breaks (was: Re: cvs commit: xml-fop/test/layoutengine/testcases normal-breaking4.xml)
Posted by Jeremias Maerki <de...@greenmail.ch>.
I think it should be relatively simple to rearrange PSLM to set up the
right page before the call to getNextBreakPoss(). What I'm wondering,
though, is why the breaks are handled during getParentArea using
information in Traits on areas and not through BreakPoss instances
during getNextBreakPoss() stage. Does anyone know? There are no such
traits described in the spec that I could find in a quick fly-over. And
IMO it doesn't make sense to do it this way. What am I missing?
On 10.02.2005 14:28:45 Jeremias Maerki wrote:
> Ouch! The PageSequenceLayoutManager has a big problem. It sets the
> reference IPD for the flow once at the beginning and then no more.
> Subsequent pages get their (correct) page master only during addArea
> stage through getParentArea(). But the flow reference area has to be set
> prior to doing any getNextBreakPoss() on a new page. So it's not
> resetPosition() methods that don't behave as I claimed in my earlier CVS
> message (although I found a few strange things with resetPosition() while
> looking at table headers/footers).
>
> On 10.02.2005 13:52:35 jeremias wrote:
> > jeremias 2005/02/10 04:52:35
> >
> > Modified: test/layoutengine/testcases normal-breaking4.xml
> > Log:
> > Adding an additional block at the end to see if a new block would behave differently.
Jeremias Maerki
Re: cvs commit: xml-fop/test/layoutengine/testcases normal-breaking4.xml
Posted by Jeremias Maerki <de...@greenmail.ch>.
Ouch! The PageSequenceLayoutManager has a big problem. It sets the
reference IPD for the flow once at the beginning and then no more.
Subsequent pages get their (correct) page master only during addArea
stage through getParentArea(). But the flow reference area has to be set
prior to doing any getNextBreakPoss() on a new page. So it's not
resetPosition() methods that don't behave as I claimed in my earlier CVS
message (although I found a few strange things with resetPosition() while
looking at table headers/footers).
On 10.02.2005 13:52:35 jeremias wrote:
> jeremias 2005/02/10 04:52:35
>
> Modified: test/layoutengine/testcases normal-breaking4.xml
> Log:
> Adding an additional block at the end to see if a new block would behave differently.
Jeremias Maerki