Re: Wrong link to source download site

[Jeremias Maerki]

Website redeployed. I guess I need to switch back to SVN deployment so
everyone can do it. Will do ASAP.

On 11.01.2007 05:45:59 The Web Maestro wrote:
> On 1/10/07, Yannick Valot <[EMAIL PROTECTED]> wrote:
> > Trouble is, http://www.apache.org/dyn/closer.cgi/xml/fop
> > eventually leads you to the old xml/fop directories, which are still
> > available (maybe to keep old links working), contain lots of old data,
> > fop-current files which certainly aren't current any more, and a subtitle
> > announcing 0.20.5 as the state of the art
> >
> > You certainly want to correct that link, and maybe to consider updating the
> > old download pages ;-). It took me a whole minute to understand what was
> > wrong.
> 
> I've updated the page, which will go LIVE the next time someone
> re-generates the site (and since this is release time, that's fairly
> often!). Thanks for the report!
> 
> > Keep up the good work on Fop !
> >
> > Yannick Valot.
> 
> Thanks for the kind words, and for reporting this glitch!
> 
> -- 
> Regards,
> 
> The Web Maestro
> -- 
> <[EMAIL PROTECTED]> - 
> My religion is simple. My religion is kindness.
> - HH The 14th Dalai Lama of Tibet



Jeremias Maerki

Re: Wrong link to source download site

[The Web Maestro]

On 1/10/07, Yannick Valot <[EMAIL PROTECTED]> wrote:

Trouble is, http://www.apache.org/dyn/closer.cgi/xml/fop
eventually leads you to the old xml/fop directories, which are still
available (maybe to keep old links working), contain lots of old data,
fop-current files which certainly aren't current any more, and a subtitle
announcing 0.20.5 as the state of the art

You certainly want to correct that link, and maybe to consider updating the
old download pages ;-). It took me a whole minute to understand what was
wrong.


I've updated the page, which will go LIVE the next time someone
re-generates the site (and since this is release time, that's fairly
often!). Thanks for the report!


Keep up the good work on Fop !

Yannick Valot.


Thanks for the kind words, and for reporting this glitch!

--
Regards,

The Web Maestro
--
<[EMAIL PROTECTED]> - 
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet

Re: Announcements refused

[J.Pietschmann]

Florent Georges wrote:

  I can take care of that, if you want.


I sent it to the XSL list just a minute ago. Thank you for the
offer anyway.

J.Pietschmann

Re: Announcements refused

[Florent Georges]

Simon Pepping wrote:

> On Tue, Jan 09, 2007 at 09:28:26PM +0100, J.Pietschmann wrote:

> > Oh, and the Mulberry XSL list seems to have been left out.

> That is also a subscribers-only list, and I am not subscribed.

  I can take care of that, if you want.

  Regards,

--drkm



























___ 
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! 
Profitez des connaissances, des opinions et des expériences des internautes sur 
Yahoo! Questions/Réponses 
http://fr.answers.yahoo.com

Wrong link to source download site

[Yannick Valot]

Hello,

I wanted to download fop-0.93, went to
http://xmlgraphics.apache.org/fop/download.html and noticed that the
hypertext link to the source distribution mirrors is outdated. It points to
http://www.apache.org/dyn/closer.cgi/xml/fop instead of
http://www.apache.org/dyn/closer.cgi/xmlgraphics/fop. The link for the
binaries is correct.

Trouble is, http://www.apache.org/dyn/closer.cgi/xml/fop eventually leads
you to the old xml/fop directories, which are still available (maybe to keep
old links working), contain lots of old data, fop-current files which
certainly aren't current any more, and a subtitle announcing 0.20.5 as the
state of the art

You certainly want to correct that link, and maybe to consider updating the
old download pages ;-). It took me a whole minute to understand what was
wrong.

Keep up the good work on Fop !

Yannick Valot.

Re: FOP Memory issues (fwd from fop-users)

[Jess Holle]

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 -- 
whatever's present.  I don't want to step "up" to 0.93 and discover 
memory usage for things that used to work in 0.20.5 is many times higher 
or such, though...


--
Jess Holle

Re: FOP Memory issues (fwd from fop-users)

[Andreas L Delmelle]

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:


Property lists themselves are no longer alive in the snapshot, it
seems. I don't suppose they are that much of a problem. They are
meant to be in scope for only a very brief interval (best case: from
PropertyListMaker.make() until FObj.bind())

Hmm, what are the 80K+ ArrayLists and their backing Object[] then?



That remains the question, of course...
If it had been the PropertyLists, there would also be 80K instances  
of StaticPropertyList.


BTW: PropertyLists use plain arrays of Property[] (not ArrayLists)



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.


I have read in relation to Java performance tuning that, if you know  
in advance which type of element will be stored in a Collection, it  
almost always pays off to write your own implementation... In this  
case, we could add a FONodeList class, that implements the  
java.util.List interface, and have it backed by a FONode[].


This could at least drastically reduce the number of casts made in  
the fo package.


Hmm, OK, this is such a good idea that I might even get started on it  
right away :)



Cheers,

Andreas

Re: Announcements refused

[Simon Pepping]

On Tue, Jan 09, 2007 at 09:28:26PM +0100, J.Pietschmann wrote:
> Simon Pepping wrote:
> >[EMAIL PROTECTED]
> 
> I took care of that.

Thanks.
 
> We might need to annotate the lists announcements are sent to by
> subscribed team members :-)

I will add a note to the release page.
 
> Oh, and the Mulberry XSL list seems to have been left out.

That is also a subscribers-only list, and I am not subscribed.

Simon

-- 
Simon Pepping
home page: http://www.leverkruid.eu

Re: FOP Memory issues (fwd from fop-users)

[Andreas L Delmelle]

On Jan 10, 2007, at 04:50, Manuel Mall wrote:


On Wednesday 10 January 2007 03:42, Andreas L Delmelle wrote:


Property lists themselves are no longer alive in the snapshot, it
seems. I don't suppose they are that much of a problem. They are
meant to be in scope for only a very brief interval (best case: from
PropertyListMaker.make() until FObj.bind())

Hmm, what are the 80K+ ArrayLists and their backing Object[] then?



That remains the question, of course...
If it had been the PropertyLists, there would also be 80K instances  
of StaticPropertyList.


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.



Cheers,

Andreas

Re: FOP Memory issues (fwd from fop-users)

[richardw]

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 the originals weren't GC'ed at the time of the snapshot...
 > >
 > I assumed the snapshot shows only reachable objects, i.e. objects not 
 > eligible for garbage collection. Otherwise it could be seriously 
 > misleading.

The whole thing bombs out with an OutOfMemoryError. If it didn't I
wouldn't be spending my time dealing with it :) The contract for
this explicitly says that garbage collection will have called before
then.

Richard