Re: [PATCH] Support for percentages and table-units

[J.Pietschmann] The layout context has the actual IPD MinOptMax. There is no inherent reason it should have a link to a parent context or the property subsystem, it's only necessary to have a method to resolve a property expression given a set of MinOptMax for the various traits which can be used a

cvs commit: xml-fop build.xml

pbwest 2004/02/18 20:00:13 Modified:.Tag: FOP_0-20-0_Alt-Design build.xml Log: Updated Licence to 2.0 Revision ChangesPath No revision No revision 1.37.2.11 +13 -48xml-fop/build.xml Index: build.xml =

cvs commit: xml-fop lic_to_2

pbwest 2004/02/18 19:59:10 Modified:bin Tag: FOP_0-20-0_Alt-Design lic_to_2 .Tag: FOP_0-20-0_Alt-Design lic_to_2 Log: Fix the backtrack churning on long files Revision ChangesPath No revision No revision

cvs commit: xml-fop/src/codegen xml-lang.xml xml-lang.xsl

pbwest 2004/02/18 19:57:52 Modified:src/codegen Tag: FOP_0-20-0_Alt-Design xml-lang.xml xml-lang.xsl Log: Updated Licence to 2.0 Revision ChangesPath No revision No revision 1.1.2.3 +13 -47xml-fop/src/

Java thory and proctice: Garbase collection and performance

I noticed this artcle on Developer Works: Java theory and practice: Garbage collection and performance http://www-106.ibm.com/developerworks/library/j-jtp01274.html Something to read on Thursday. -- John Austin <[EMAIL PROTECTED]>

cvs commit: xml-fop build-notes NOTICE.txt

pbwest 2004/02/18 18:17:11 Removed: .Tag: FOP_0-20-0_Alt-Design build-notes NOTICE.txt Log: Not required - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: xml-fop lic_to_2

pbwest 2004/02/18 17:49:30 Modified:.Tag: FOP_0-20-0_Alt-Design lic_to_2 Log: Tidied up the start and end conditions for the changes. Revision ChangesPath No revision No revision 1.1.2.2 +2 -3 xml-fop/Attic/lic_to_2

cvs commit: xml-fop/bin lic_to_2

pbwest 2004/02/18 17:48:41 Modified:bin Tag: FOP_0-20-0_Alt-Design lic_to_2 Log: Tidied up the start and end conditions for the changes. Revision ChangesPath No revision No revision 1.1.2.2 +2 -3 xml-fop/bin/Attic/lic_t

Re: [PATCH] Support for percentages and table-units

--- Simon Pepping <[EMAIL PROTECTED]> wrote: > > In my view FOP consists of a number of subsystems > that are ordered > from upstream to downstream. The FO tree is the most > upstream system, > the area tree (or objects that are constructed by a > renderer) is the > most downstream system. Informa

RE: [PATCH] Support for percentages and table-units

> is being interrogated/perceived/discussed... Sorry, it's late here... > You are IMO very correct by stating that 'if the Layout info can > be reused, > so can the AT and the renderer', however, if I interpret correctly, the > latter two are designed to dispose of their created objects ASAP.

RE: [PATCH] Support for percentages and table-units

> -Original Message- > From: Simon Pepping [mailto:[EMAIL PROTECTED] > > In my view FOP consists of a number of subsystems that are ordered > from upstream to downstream. The FO tree is the most upstream system, > the area tree (or objects that are constructed by a renderer) is the > most d

Re: [PATCH] Support for percentages and table-units

On Tue, Feb 17, 2004 at 04:52:10PM -0800, Glen Mazza wrote: > --- Finn Bock <[EMAIL PROTECTED]> wrote: > > > > The layout dimension that is stored in the FO tree > > is constantly updated > > during discovery of BreakPoss'es and is never > > reused, not even when a > > block is split over a break

Re: [PATCH] Support for percentages and table-units

On Tue, Feb 17, 2004 at 09:31:52PM +0100, Finn Bock wrote: > > [J.Pietschmann] > > >The layout context has the actual IPD MinOptMax. There is no > >inherent reason it should have a link to a parent context or the > >property subsystem, it's only necessary to have a method to > >resolve a property