Hello Victor,

thanks for your answer. This subject is really critical for my application,
at the moment. So my only chance is to implement it myself.  At least, I'm
going to try. In case of succes, I'll post changes in this mailing list...

Tibor

----- Original Message -----
From: "Victor Mote" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, December 02, 2003 1:03 AM
Subject: RE: Connection between FO object and Area object


> Tibor Vyletel wrote:
>
> > I'm using FOP in one my project. I have created a new renderer
(rendering
> GEF figures),
> > but recently I got stuck with one very unpleasant problem:
>
> > I was persuaded that I will be able to determine original ID atribute of
a
> fo element in
> > corresponding Area class, but now I'm disappointed, because there seem
to
> be no way of
> > doing it. I was trying Trait.ID_AREA and Trait.ID_LINK but these are not
> currently used.
> > Areas don't have a reference to FONodes. Is there any other way how to
get
> to FO objects
> > (or at least ID attribute) during visual rendering?
>
> ...
>
> > PS: I use HEAD version of FOP.
>
> I became aware of this when I was trying to port the maintenance branch
> layout into the trunk. It is, in fact, the issue that stopped my progress
> when I was last able to work on that project about 8 weeks ago. I hope to
> get back to it again sometime in the next week or two. It appears that IDs
> were implemented in maintenance branch code, but never in the trunk. I was
> just starting into figuring out what the new design is, when I got
> sidetracked. I suppose that the correct approach in the new design is to
use
> the TRAIT constructs that you have noted, but I am not sure. If anybody
> knows how this is *supposed* to work in the new design, please let me
know.
>
> The short answer is that I think this problem will eventually be fixed,
but
> I am not sure when.
>
> Victor Mote
>
>

Reply via email to