Hi Arved,
There are a couple of reasons that it only has a URL.
If the page is going to be serialized we don't want to serialize an image.
There is no advantage to having a reference to the image and it would make
it harder to keep track of references for caching.
The URL is used as a key to
I've got a comment below concerning the PS renderer which I think may be
important when working on the image stuff.
snip/
So in the FOTree it only grabs the image (using the URL) if the size of
the image is needed. The image is then in the cache with the URL as the
key. When the renderer
with the URL, etc etc, that _this_ image is the
FopAbstractImage or an advanced version of same?
Regards,
Arved
-Original Message-
From: Keiron Liddle [mailto:[EMAIL PROTECTED]]
Sent: March 18, 2002 4:22 AM
To: [EMAIL PROTECTED]
Subject: Re: Image Handling Question
Hi Arved
On 2002.03.18 12:45 Arved Sandstrom wrote:
So I don't disagree, although I'd get pedantic and point out that, yes,
we're setting _a_ size on the viewport, but that is not necessarily the
size of the image. But layout doesn't care - it only cares about the size
of
the viewport.
Yes there
Keiron or Karen,
I have a quick question. This is mostly because I am unfamiliar with the
code. As it stands right now org.apache.fop.area.inline.ImageArea does not
look like something that the layout process can use; it also doesn't look
like something that the renderer can use because it
