While investigating the multi-threading issues in the maint-branch I
came across the following:
Currently, in the context of the PDF renderer, every FopImage is closed
as soon as it's written to the target file. The next time the same
image/url is used it has to be reloaded. This is not true for
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13406.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14290.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
keiron 2002/11/06 02:02:29
Modified:src/org/apache/fop/layoutmgr PageLayoutManager.java
src/org/apache/fop/fo/pagination PageSequence.java
Log:
layout correct static region
improved docs and style
Revision ChangesPath
1.23 +129 -27
Jeremias Maerki wrote:
Currently, in the context of the PDF renderer, every FopImage is closed
as soon as it's written to the target file. The next time the same
image/url is used it has to be reloaded. This is not true for the other
renderers, where the images are really being cached. The calls
Thanks for answering. Do you have a pointer to some documentation
describing that side-effect free policy?
So, do I get you right that the close() calls can safely be removed
because the semantic change I described is irrelevant? That would be
nice because it's easy to fix.
On Wed, 06 Nov 2002
Hi,
I have arial.xml,arialbd.xml,ariali.xml,arialbi.xml,ariblk.xml under my Fop-0.18.1-DEV dir. But during the XML to PDF convertions through XSL using XSLT processor, i am facing problem. The FO with font-family "Arial" whichused is not displayed after the PDF conversion. Does the Windows-NT and
On Wednesday 06 November 2002 09:55, Jeremias Maerki wrote:
. . .
fo:external-graphic src=url(http://localhost/mydynamicimage)
xmlns:fop=http://xml.apache.org/fop; fop:disable-caching=true/
. . .
There are some fox: extensions already IIRC (never used them though, but
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14294.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14294.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14294.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hello there!
I have posted my awt viewer patch to the bugzilla patch queue. Please review.
I tested the patch (english and russian languages only though) and it looks ok
to me.
PS.A bit of nitpicking: Images catalog looks bizarre among other packages,
should be images.
--
Oleg Tkachenko
Jeremias Maerki wrote:
Thanks for answering. Do you have a pointer to some documentation
describing that side-effect free policy?
Unfortunately not. xsl requirements and xsl proposal states intensions for xsl
to be side-effect free language, like its dad dsssl, but as side-effect free
xslt
On Wed, 2002-11-06 at 12:01, Bertrand Delacretaz wrote:
On Wednesday 06 November 2002 09:55, Jeremias Maerki wrote:
. . .
fo:external-graphic src=url(http://localhost/mydynamicimage)
xmlns:fop=http://xml.apache.org/fop; fop:disable-caching=true/
. . .
There are some fox: extensions
On Wed, 2002-11-06 at 08:09, Victor Mote wrote:
I just went looking in the archives for this discussion thought I saw
pieces of it, but could not find what I was looking for -- namely, what
theories you guys had proposed / agreed upon. This is related to the font
work that I have started,
On Tue, 2002-11-05 at 11:56, Oleg Tkachenko wrote:
Hello there!
I see forrest at the web site and it looks terrific! Well done, my
congratulations.
Sorry for predating any official announce :)
Lots more to do but I think it is a good start.
Need to brighten up or change the logo. Maybe
On Wednesday 06 November 2002 12:31, Keiron Liddle wrote:
. . .
What sort of jfor extensions are there, what do they do?
We have jfor:style to define RTF styles (similar to CSS classes in concept)
on the generated RTF elements. A concept that does not exist in XSL-FO as
it doesn't make sense
On Wednesday 06 November 2002 10:03, Keiron Liddle wrote:
. . .
Lots more to do but I think it is a good start.
Great job indeed!
I've also been looking at Forrest more closely recently, already very usable
and looks even more promising.
Need to brighten up or change the logo. Maybe we should
On Wed, 2002-11-06 at 13:12, Oleg Tkachenko wrote:
Hello there!
I have posted my awt viewer patch to the bugzilla patch queue. Please review.
I tested the patch (english and russian languages only though) and it looks ok
to me.
Great! I'll take a look at see it in action.
PS.A bit of
Hello there!
Patch queue looks very good, and what about introducing one more queue for
feature requests? We can identify them among other bugzilla entries by
something like [FREQ] in a subject line. Last hour I noticed 3 small requests
to be considered, but my monitor is full of those to do
On Wednesday 06 November 2002 14:58, Oleg Tkachenko wrote:
. . .
Patch queue looks very good, and what about introducing one more queue for
feature requests?
. . .
I think these can be identified by the severity=enhancement field of
bugzilla issues, isn't that sufficient?
Maybe this must be
On Wed, 2002-11-06 at 14:45, Keiron Liddle wrote:
On Wed, 2002-11-06 at 13:12, Oleg Tkachenko wrote:
Hello there!
I have posted my awt viewer patch to the bugzilla patch queue. Please review.
I tested the patch (english and russian languages only though) and it looks ok
to me.
keiron 2002/11/06 06:30:16
Modified:src/org/apache/fop/apps AWTStarter.java
src/org/apache/fop/render/awt AWTRenderer.java
src/org/apache/fop/viewer Command.java GoToPageDialog.java
PreviewDialog.java PreviewDialogAboutBox.java
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14294.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
keiron 2002/11/06 07:07:04
Modified:src/org/apache/fop/area Area.java RegionViewport.java
src/org/apache/fop/area/inline Viewport.java
Log:
clone and serialize area traits
Revision ChangesPath
1.12 +6 -2 xml-fop/src/org/apache/fop/area/Area.java
Fellow FOP developers,
would you mind using the interface instead of the implementation where
possible? Map instead of HashMap, List instead of ArrayList. I've seen
this habit in a number of places and not only by Keiron! I've made it a
habit to follow this pattern:
import java.util.List;
[..]
On Wednesday 06 November 2002 16:18, Jeremias Maerki wrote:
. . .
would you mind using the interface instead of the implementation where
possible?
big +1.
The only drawback is when you need to clone Collections, but the benefits far
outweigh this I think.
Maybe a minimal best practices or
On Wed, 6 Nov 2002 16:25:24 +0100 Bertrand Delacretaz wrote:
On Wednesday 06 November 2002 16:18, Jeremias Maerki wrote:
. . .
would you mind using the interface instead of the implementation where
possible?
big +1.
Thanks for your support.
The only drawback is when you need to clone
I wholeheartedly agree. This is really just good style in general.
Maybe we should seriously consider a FOP developer coding standard and start writing
it down and putting it on the site. I'd offer to help with that.
-Original Message-
From: Jeremias Maerki
Bertrand Delacretaz wrote:
Maybe a minimal best practices or style guide document for developers
would be nice, I don't think there is one already?
Some time ago Jeremias has promised us that already :)
--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel
keiron 2002/11/06 07:36:29
Modified:src/org/apache/fop/fo/pagination Region.java RegionBody.java
src/org/apache/fop/layoutmgr AbstractLayoutManager.java
src/org/apache/fop/render AbstractRenderer.java
src/org/apache/fop/render/pdf
Well, if he needs help getting it done, I'm available.
-Original Message-
From: Oleg Tkachenko [mailto:olegt;multiconn.com]
Sent: Wednesday, November 06, 2002 10:32 AM
To: [EMAIL PROTECTED]
Subject: Re: interface instead of implementation
Bertrand Delacretaz wrote:
Maybe a minimal
keiron 2002/11/06 07:46:55
Modified:src/org/apache/fop/layoutmgr
BlockContainerLayoutManager.java
src/org/apache/fop/layoutmgr/list Item.java
ListBlockLayoutManager.java
ListItemLayoutManager.java
On Wednesday 06 November 2002 16:31, Rhett Aultman wrote:
. . .
Maybe we should seriously consider a FOP developer coding standard and
start writing it down and putting it on the site. I'd offer to help with
that.
. . .
How about using a wiki page (web page where everyone can very easily
You get my +1. A Wiki for a draft, followed by a vote for commitment to a less
malleable form, is the best way I could see for us to do this.
-Original Message-
From: Bertrand Delacretaz [mailto:bdelacretaz;codeconsult.ch]
Sent: Wednesday, November 06, 2002 10:48 AM
To: [EMAIL
Hey, Rhett, that would be cool. But it involves reading through that
whole discussion again, trying to find a common line and distill that
into a nice little document. As I've said, I'll have time to do it, just
not now. If you take it, THANKS A LOT!
On Wed, 6 Nov 2002 10:37:12 -0500 Rhett
+1
On Wed, 6 Nov 2002 16:48:11 +0100 Bertrand Delacretaz wrote:
On Wednesday 06 November 2002 16:31, Rhett Aultman wrote:
. . .
Maybe we should seriously consider a FOP developer coding standard and
start writing it down and putting it on the site. I'd offer to help with
that.
. . .
keiron 2002/11/06 07:57:11
Modified:test/resources/fop/image size.fo
test/resources/fop/svg embed.fo
Log:
improved layout a bit, added some more examples of scaling
Revision ChangesPath
1.2 +31 -4 xml-fop/test/resources/fop/image/size.fo
On Wed, 2002-11-06 at 16:48, Bertrand Delacretaz wrote:
How about using a wiki page (web page where everyone can very easily write
and edit) to work together on a draft style guide. including links to
existing guides so we don't reinvent the wheel?
If I get some +1s on this I'll setup the
How about using a wiki page [ ... ]
+1
-- Scott
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Sorry, Keiron, for explicitly mentioning you. I was just working in the
maint branch seeing all those ArrayLists (former Vectors) and HashMaps
(former Hashtables) that are creeping through all the code. And then
your CVS commit came... I know I can be an elephant in a porcelaine
store sometimes.
Wow, that's a quick vote...
I have setup the page at
http://codeconsult.ch/wiki/index.php/FopDevelopersStyleGuide
with a most basic style guide skeleton.
I have to run now, but feel free to work on it. Make sure you keep copies of
what you write, I cannot guarantee backups on this server yet.
keiron 2002/11/06 08:25:17
Modified:.status.xml
Log:
updated a number of previous changes
Revision ChangesPath
1.14 +35 -7 xml-fop/status.xml
Index: status.xml
===
RCS file:
Jeremias Maerki wrote:
I'm going a step further and I'm thinking about providing a development
tool for FOP. We've developed a simple one at work where we could
specify either FO or XML/xSLT file and an output format (FO, PDF, PS etc.).
Then we have that big Process button that runs the document
You mentioned HashMaps briefly here. I suppose I could try auditing the code and
answering my own question here, but I have very little free time in general.
(Hopefully, I'll have more free time after Saturday...I've spent a lot of time for
weeks studying for the GRE). So, I'll just ask- has
For caching and if done correctly, yes, there could be benefits.
WeakReferences can be used if you have objects you want to keep but
you're not angry when they get swept away by the GC. Good for keeping
images and fonts in memory, but for overall FOP I don't see any use case.
Or can anyone think
Mostly it was for caching benefits. As I said, though, I haven't read enough code to
know. I just thought I'd throw it out as a possibile way to save on memory usage when
FOP processes large documents. *shrug* ;)
-Original Message-
From: Jeremias Maerki
This is how it used to work:
o anywhere in FOP formatting
- load image, if same URL was not loaded before and find out the space
needed for the image.
- keep list of processed files.
o PDF Renderer:
- generate XObject, if XObject of same URL was not generated before. Delete
image buffer:
Keiron Liddle wrote:
I had a few problems with character encoding and line endings so check
that it is right.
The code looks fine, but all Viewer*.property files seem to be CRCRLF-ed
:( I have no idea why.
--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel
Oleg Tkachenko wrote:
Jeremias Maerki wrote:
Thanks for answering. Do you have a pointer to some documentation
describing that side-effect free policy?
Unfortunately not. xsl requirements and xsl proposal states intensions
for xsl to be side-effect free language, like its dad dsssl, but as
roopashree s wrote:
I have arial.xml,arialbd.xml,ariali.xml,arialbi.xml,ariblk.xml under my
Fop-0.18.1-DEV dir. But during the XML to PDF convertions through XSL
using XSLT processor, i am facing problem. The FO with font-family
Arial which used is not displayed after the PDF conversion. Does
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14319.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Rhett, Jeremias,
I was hoping there might be a little more detailed discussion here. I
have no experience of WeakHashMaps or the various Reference objects, but
I have been thinking about using Reference objects, rather than direct
references, to point to the Nodes in my Tree, with the idea
Jeremias,
I have no objection at all, as long as it costs nothing. It is free,
isn't it?
Peter
Jeremias Maerki wrote:
Fellow FOP developers,
would you mind using the interface instead of the implementation where
possible? Map instead of HashMap, List instead of ArrayList. I've seen
this
keiron 2002/11/06 23:31:55
xml-fop/src/documentation/content/xdocs/design - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Wed, 06 Nov 2002 23:59:53 +0200 Oleg Tkachenko wrote:
Keiron Liddle wrote:
I had a few problems with character encoding and line endings so check
that it is right.
The code looks fine, but all Viewer*.property files seem to be CRCRLF-ed
:( I have no idea why.
That's a problem all
keiron 2002/11/06 23:44:58
Modified:src/org/apache/fop/viewer/resources Viewer.properties
Viewer_cs.properties Viewer_de.properties
Viewer_fi.properties Viewer_fr.properties
Viewer_it.properties
57 matches
Mail list logo
