Trait.ID_AREA

[Tibor Vyletel <ti...@centrum.sk>]

Hi guys,

In previous versions (builds) of FOP areas have had set ID_AREA trait in order to allow identification of original FONodes (and XML elements) they had been created from. Why is this feature missing in recent builds (1.0DEV)? Is there any other possibility how to connect Area --> FONode --> XML Element data entities?


Thanks

Tibor Vyletel

Re: Trait.ID_AREA

[Chris Bowditch <bo...@hotmail.com>]

Tibor Vyletel wrote:

> Hi guys,
>  
> In previous versions (builds) of FOP areas have had set ID_AREA trait in 
> order to allow identification of original FONodes (and XML elements) 
> they had been created from. Why is this feature missing in recent builds 
> (1.0DEV)? Is there any other possibility how to connect Area --> FONode 
> --> XML Element data entities?

I suspect that the ID_AREA property has been removed from FObj as a result of 
the property re-work. Perhaps one of the property gurus will be able to 
comment further.

Polite request: please dont post to the list in HTML, its considered bad 
etiquette.

Chris

RE: Trait.ID_AREA

["Andreas L. Delmelle" <a_...@pandora.be>]

> -----Original Message-----
> From: Tibor Vyletel [mailto:tivy@centrum.sk]


Hi,

> In previous versions (builds) of FOP areas have had set ID_AREA trait
> in order to allow identification of original FONodes (and XML elements)
> they had been created from.
> Why is this feature missing in recent builds (1.0DEV)?

This, I think, is because in HEAD, the Layout Managers are responsible for
adding the Areas based on the FOBjs that were used to create them.

> Is there any other possibility how to connect Area -->
> FONode --> XML Element data entities?

AFAICT, the LM doesn't provide a way to allow other objects to talk to its
FObj directly. For instance, there is a setFObj() method, but no getFObj()
that returns it (--and, come to think of it, this shouldn't be necessary)
IIC, then it should be possible to trace it up to the point where the Area
gets added to the AreaTree by the LM ( addArea() or addChild() ) Maybe you
can insert a few steps there to pass the FONode / FObj id to the Area.


Hope this offers a bit of help....


Cheers,

Andreas