On Sun, Feb 15, 2004 at 04:41:46PM -, [EMAIL PROTECTED] wrote:
--- Additional Comments From [EMAIL PROTECTED] 2004-02-15 16:41 ---
Good catch Simon, thanks for taking time to look at it. The NPE is due to a
missing implementation of getNumeric() in RelativeNumericProperty (which
Finn Bock wrote:
If an expression reference another expression in a parent fo, the parent
fo expression must be evaluated against the LayoutContext that was in
effect for the parent fo and *not* against the child fo LayoutContext.
fo:block id=a border-start-width=10%
fo:block id=b
John Austin wrote:
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.
Nice read, however, they don't talk about constructors. There
are still arguments
[Simon Pepping]
I like the patch and the way RelativeNumericProperty holds and
evaluates an expression tree (except my different preference for
storing layout information, as discussed). This is really nice and
works well:
v = (((0mpt +(4000mpt +20.0%)) +0mpt) +0mpt)
I found a few things that
On Thu, 2004-02-19 at 17:53, J.Pietschmann wrote:
John Austin wrote:
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.
Nice read,
