On Jan 14, 2007, at 22:51, J.Pietschmann wrote:
Andreas L Delmelle wrote:
Based on Jörgs statistics, I'd say that the number of children
will most likely never reach the level where using direct index-
based access (ArrayList) has its benefits over traversing a tree
of references
Andreas L Delmelle wrote:
Based on Jörgs statistics, I'd say that the number of children will most
likely never reach the level where using direct index-based access
(ArrayList) has its benefits over traversing a tree of references
(LinkedList).
There may be FOs, specifically fo:flow and
On Jan 12, 2007, at 13:00, [EMAIL PROTECTED] wrote:
snip /
Just a quick comment on this, given the above stats you might
consider having a single Object field and switch the type of object
from the actual child (when there is a single child) to a List of
children when there are multiple
Hi all,
Andreas L Delmelle [EMAIL PROTECTED] wrote on 01/11/2007 05:24:36
PM:
On Jan 11, 2007, at 22:31, J.Pietschmann wrote:
Quite some time ago I did some statistics on number of children
of FOs, using the FOP examples and FO files from bug reports.
The breakdown was roughly the
Andreas L Delmelle writes:
I'd say the 80K ArrayLists are simply the childNodes lists of all
those FObj (TableCells and Blocks), and that those are, in most
cases, lists of only one element.
This is correct - for most instances,
Richard
On Jan 11, 2007, at 10:02, [EMAIL PROTECTED] wrote:
Andreas L Delmelle writes:
I'd say the 80K ArrayLists are simply the childNodes lists of all
those FObj (TableCells and Blocks), and that those are, in most
cases, lists of only one element.
This is correct - for most instances,
Which
Andreas L Delmelle wrote:
Which brings us to another important piece of information that would be
interesting to know: how big are each of those instances?
Quite some time ago I did some statistics on number of children
of FOs, using the FOP examples and FO files from bug reports.
The
On Jan 11, 2007, at 22:31, J.Pietschmann wrote:
Quite some time ago I did some statistics on number of children
of FOs, using the FOP examples and FO files from bug reports.
The breakdown was roughly the following
~50% no children, mostly FOText nodes and FOs like region-body
and
Manuel Mall writes:
On Wednesday 10 January 2007 03:42, Andreas L Delmelle wrote:
White-space nodes? Could also be an effect of the white-space
collapsing. Long shot, but theoretically, 'white-space-handling' in
FOText means 'replace FOText.ca with a copy minus a few characters',
if
On Jan 10, 2007, at 20:39, Andreas L Delmelle wrote:
On Jan 10, 2007, at 04:50, Manuel Mall wrote:
On Wednesday 10 January 2007 03:42, Andreas L Delmelle wrote:
snip /
Property lists themselves are no longer alive in the snapshot, it
seems. I don't suppose they are that much of a problem.
For all the talk of FOP memory issues, does anyone have any information
as to whether the problem is worse than in FOP 0.20.5 -- and, if so, by
how much?
I'm considering upgrading what we require/bundle to 0.93 and currently
have reflection code allowing operation against 0.93 or 0.20.5 --
Andreas L Delmelle writes:
If I remember correctly, that was precisely the problem, since
Cliff's report consists of one giant table. It's supposed to look
like one uninterrupted flow, so figuring out where the page-sequences
should end is next to impossible... (or IOW: sorting that
On Tuesday 09 January 2007 18:13, [EMAIL PROTECTED]
wrote:
Andreas L Delmelle writes:
If I remember correctly, that was precisely the problem, since
Cliff's report consists of one giant table. It's supposed to look
like one uninterrupted flow, so figuring out where the
page-sequences
Perhaps the flyweight pattern, described by the GoF, may be of use to
whoever is going to look into an implementation strategy.
http://en.wikipedia.org/wiki/Flyweight_pattern gives a decent example.
amin
On 1/9/07, Manuel Mall [EMAIL PROTECTED] wrote:
On Tuesday 09 January 2007 18:13, [EMAIL
Richard a écrit :
snip/
I'm also currently reading through Knuth's Digital Typography. Can anyone
point out any sections I should pay particular attention to w.r.t. FOP's
usage,
(Digital Typography caught my eyes. I'll try to respond to the rest
later.)
Chapter 3, Breaking Paragraphs Into
On Tue, 2007-01-09 at 16:52 +0100, Vincent Hennebert wrote:
Richard a écrit :
snip/
I'm also currently reading through Knuth's Digital Typography. Can anyone
point out any sections I should pay particular attention to w.r.t. FOP's
usage,
(Digital Typography caught my eyes. I'll try to
On Jan 9, 2007, at 14:11, Manuel Mall wrote:
snip /
What are the 81632 instances of class char[]? I assume this is the
text
in the table cells. But why are there more than twice as many as there
are table cells?
Hehe, see my little remark about the TextLM... In its initialize()
method (I
On Jan 9, 2007, at 18:46, Andreas L Delmelle wrote:
On Jan 9, 2007, at 14:11, Manuel Mall wrote:
snip /
What are the 81632 instances of class char[]? I assume this is the
text
in the table cells. But why are there more than twice as many as
there
are table cells?
Hehe, see my little
On Jan 5, 2007, at 16:20, Jeremias Maerki wrote:
Adding page breaks will not be enough, BTW. But you already noticed
that.
FOP can currently only release memory at the end of a page-
sequence. So
instead of creating page-breaks, try to restart a new page-
sequence. The
memory usage should
19 matches
Mail list logo
