I finally got the danged thing to download from the svn repo. Took me all day
to figure out how to get around our doggone proxy. I'm going to try building
it and see if that will fix my problem. In the interim if somebody could help
me with an algorithm I'd be ever so grateful. I'm an ameture at
Ok, I've been toiling over this for far too long and I'm 'bout to be fired as
a result. I really need some help. My report works as follows. Depending on
what option the report runs with there will be nested elements
representing the layout of the data respective to the UI selection. each
grou
Yeah, I tried just running the raw XSL-FO through and still got an out of
memory. I've also had the biggest problem getting the SVN source to build. If
someone could check it out and send it to me in an archive (any archive type,
I run Linux) I'd appreciate it. You see This is my first time usin
On Dec 9, 2005, at 17:26, Andreas L Delmelle wrote:
On Dec 9, 2005, at 15:33, Clifton Craig wrote:
Why is it that I would get the same OutOfMemoryError on the XEP
personal edition?
That's what has me wondering if it's really something wrong with
my FO syntax or
my stylesheet.
It has me won
On Dec 9, 2005, at 15:33, Clifton Craig wrote:
Why is it that I would get the same OutOfMemoryError on the XEP
personal edition?
That's what has me wondering if it's really something wrong with my
FO syntax or
my stylesheet.
It has me wondering about one section in my stylesheet that matches
Thank you all so much. I have another question though. Why is it that I would
get the same OutOfMemoryError on the XEP personal edition? That's what has me
wondering if it's really something wrong with my FO syntax or my stylesheet.
It has me wondering about one section in my stylesheet that mat
The layout engine of 0.90alpha1 works differently. It's a bit difficult
to compare the two versions. But I'd have to say the same optimization
is currently not possible in 0.90/Trunk unless we extend the breaking
algorithm to support a first/best fit strategy so the objects can be
released early (i
You know what? Is the patch already in the new Alpha release? Cause if it is
then it's not worth my time applying it to FOP-0.20.2. I've already tried my
stylesheet with the alpha version and I still have the memory issue.
On Thursday 08 December 2005 10:17 pm, Andreas L Delmelle wrote:
> On Dec
On Dec 8, 2005, at 23:01, Clifton Craig wrote:
I'm banging my head on this so maybe I'll look into the quick fix
since this
is the 2nd or 3rd time someone has brought it up. Is it a jar or
something
that would be easy to install?
Not exactly... although not too much effort either.
Check o
I'm banging my head on this so maybe I'll look into the quick fix since this
is the 2nd or 3rd time someone has brought it up. Is it a jar or something
that would be easy to install?
On Thursday 08 December 2005 3:43 pm, J.Pietschmann wrote:
> Clifton Craig wrote:
> > So the only time tables are
Clifton Craig wrote:
So the only time tables are realeased are at the end of a page sequence?
Yes. The problem is actually all the stuff used during content
layout, which is otherwise released after a page has been rendered.
There is a quick fix in the source repository for this.
J.Pietschmann
Chris Bowditch wrote:
Clifton Craig wrote:
J,
So the only time tables are realeased are at the end of a page
sequence? That would explain my dilemma. Even though I use multiple
smaller tables per row instead of one big table all of the smaller
tables are held until the page sequence ends?
Clifton Craig wrote:
Chris,
My apologies as I didn't mean those comments to sting. What I should have said
was, "that sux for me". Or even better, "it sux to be me". I was only venting
from my current situation and I wasn't attempting to trash talk the product
at all. FOP is the perfect fit
Chris,
My apologies as I didn't mean those comments to sting. What I should have said
was, "that sux for me". Or even better, "it sux to be me". I was only venting
from my current situation and I wasn't attempting to trash talk the product
at all. FOP is the perfect fit for our project and ther
Clifton Craig wrote:
J,
So the only time tables are realeased are at the end of a page sequence? That
would explain my dilemma. Even though I use multiple smaller tables per row
instead of one big table all of the smaller tables are held until the page
sequence ends? That sux.
Non constru
On Wednesday 07 December 2005 3:46 pm, J.Pietschmann wrote:
> Clifton Craig wrote:
> > I'm still a
> > little concerned as to why I'm having memory overflow if it is the norm
> > to use one page sequence for the report body as I've done.
>
> Tables lock up objects used for content formatting for to
Clifton Craig wrote:
I'm still a
little concerned as to why I'm having memory overflow if it is the norm to
use one page sequence for the report body as I've done.
Tables lock up objects used for content formatting for too long,
they are released (together with objects representing the FO)
at
On Dec 7, 2005, at 16:12, Clifton Craig wrote:
Hi,
Thanx for your reply. Yes I do want to ultimately make it look like
it did
when I just dumped the entire report body under one page sequence,
however I
cannot use one page sequence due to memory overflow issues.
I'm still a little concerned
Andreas,
Thanx for your reply. Yes I do want to ultimately make it look like it did
when I just dumped the entire report body under one page sequence, however I
cannot use one page sequence due to memory overflow issues. I'm still a
little concerned as to why I'm having memory overflow if it is
On Dec 6, 2005, at 15:16, Clifton Craig wrote:
Hi,
I understand my stylesheet snippets are amature because that's just
what I was
when I started the project, an XSL amature.
Whoops, I hope I didn't give the impression that I was mocking your
current level of understanding XSLT... Besides
Andreas,
I understand my stylesheet snippets are amature because that's just what I was
when I started the project, an XSL amature. I am open to any and all
suggestions for improvement but understand that I am most interested in
fixing the pressing memory problem at hand. See my answer to Dave
iastically take it, and it might solve a lot of the
> performance/memory issues that are posted to the list.
>
> Dave
>
> -Original Message-
> From: Glen Mazza [mailto:[EMAIL PROTECTED]
> Sent: Monday, December 05, 2005 4:42 PM
> To: fop-users@xmlgraphics.apache.
Glen Mazza wrote:
No doubt. But 0.90alpha1 will be getting better. Very few if any
committers really understand 0.20.5 anymore, the committers who worked
on it are mostly gone today.
I reckon Joerg is a bit of an expert at 0.20.5 ;)
Chris
David Frankson wrote:
However, if you were to
take the latest source and put it into a 20.5.1, we'd probably
enthusiastically take it, and it might solve a lot of the
performance/memory issues that are posted to the list.
No doubt. But 0.90alpha1 will be getting better. Very few if any
com
On Dec 6, 2005, at 00:11, David Frankson wrote:
He is probably using the multiple page sequences to work around the
memory issues in tables. I would say that most all of us who use 20.5
do this. I've written lots of xsl:fo that does its own page
sequencing
by counting lines of data, and we
zza [mailto:[EMAIL PROTECTED]
Sent: Monday, December 05, 2005 4:42 PM
To: fop-users@xmlgraphics.apache.org
Subject: Re: Page Sequences
Clifton Craig wrote:
> I'm writing a report transform usinf XSLT for XSL-FO and I have some
basic
> questions. What's the best way to code for
On Dec 5, 2005, at 21:43, Clifton Craig wrote:
Hi,
I'm writing a report transform usinf XSLT for XSL-FO and I have
some basic
questions. What's the best way to code for multiple page sequences.
For
example I have some static content that I like to keep in the
header and
footers and I gues
Clifton Craig wrote:
I'm writing a report transform usinf XSLT for XSL-FO and I have some basic
questions. What's the best way to code for multiple page sequences. For
example I have some static content that I like to keep in the header and
footers and I guess it doesn't matter but I'd like t
28 matches
Mail list logo
